2010 MacBook Pro Intel Core 2 Duo, 2.4 GHz, with 8GB, OS X 10.8.4, Homebrew
textmate(master) $ git submodule update --init
seemed fine. Then there was:
textmate(master) $ ./configure make: *** [/Users/richarddrake/build/TextMate/Frameworks/SoftwareUpdate/fixtures/secret.pem] Error 127
but what the heck, I carried on. So then:
textmate(master) $ ninja ... [various warnings] [171/987] Run test '/Users/richarddrake/build/TextMate/Frameworks/scm/test_scm'... FAILED: /Users/richarddrake/build/TextMate/Frameworks/scm/test_scm && touch /Users/richarddrake/build/TextMate/Frameworks/scm/test_scm.run /bin/sh: line 1: 33977 Segmentation fault: 11 /Users/richarddrake/build/TextMate/Frameworks/scm/test_scm
Got another error in trying again so googled and did:
textmate(master) $ ninja scm/coerce [1/1] Skip test '/Users/richarddrake/build/TextMate/Frameworks/scm/test_scm'... textmate(master) $ ninja ... [174/808] Run test '/Users/richarddrake/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate'... FAILED: /Users/richarddrake/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate && touch /Users/richarddrake/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate.run test_SoftwareUpdate: 5 of 8 tests failed: /Users/richarddrake/puny/big/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:64: Expected (err == "Extracting archive."), found ("The requested URL returned error: 404" != "Extracting archive.") /Users/richarddrake/puny/big/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:73: Expected (err == "Extracting archive."), found ("The requested URL returned error: 404" != "Extracting archive.") /Users/richarddrake/puny/big/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:82: Expected (err == "Bad signature."), found ("The requested URL returned error: 404" != "Bad signature.") /Users/richarddrake/puny/big/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:91: Expected (err == "Bad signature."), found ("The requested URL returned error: 404" != "Bad signature.") /Users/richarddrake/puny/big/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:109: Expected (err == NULL_STR), found ("The requested URL returned error: 404" != " ") [174/808] Compile 'Frameworks/document/src/document.cc'... Frameworks/document/src/document.cc:160:24: warning: private field 'tracker' is not used [-Wunused-private-field] document_tracker_t* tracker; ^ 1 warning generated. ninja: build stopped: subcommand failed.
Tried (without knowing ninja or what this meant) this multiple times:
textmate(master) $ ninja SoftwareUpdate/coerce [1/1] Skip test '/Users/richarddrake/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate'...
which got me to:
textmate(master) $ ninja [8/26] Run test '/Users/richarddrake/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate'... FAILED: /Users/richarddrake/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate && touch /Users/richarddrake/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate.run test_SoftwareUpdate: 5 of 8 tests failed: /Users/richarddrake/puny/big/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:64: Expected (err == "Extracting archive."), found ("The requested URL returned error: 404" != "Extracting archive.") /Users/richarddrake/puny/big/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:73: Expected (err == "Extracting archive."), found ("The requested URL returned error: 404" != "Extracting archive.") /Users/richarddrake/puny/big/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:82: Expected (err == "Bad signature."), found ("The requested URL returned error: 404" != "Bad signature.") /Users/richarddrake/puny/big/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:91: Expected (err == "Bad signature."), found ("The requested URL returned error: 404" != "Bad signature.") /Users/richarddrake/puny/big/textmate/Frameworks/SoftwareUpdate/tests/t_sw_update.cc:109: Expected (err == NULL_STR), found ("The requested URL returned error: 404" != " ") ninja: build stopped: subcommand failed.
At which point googling didn't seem to shed light and I came here. Been a TextMate user since 2006, decided to download v2 on Wednesday. Great job Allan and co. I thought I'd take a look at the source because of a niggle found that I've created a GitHub issue for:
https://github.com/textmate/textmate/issues/1047
But it would be nice to tinker with other things anyway.
Regards
Richard
On 13 Jul 2013, at 14:13, Richard Drake wrote:
textmate(master) $ ./configure make: *** [/Users/richarddrake/build/TextMate/Frameworks/SoftwareUpdate/fixtures/secret.pem] Error 127
The failing line would be this (which you can try to re-run):
DST=build/Frameworks/SoftwareUpdate/fixtures make -C Frameworks/SoftwareUpdate/fixtures
Although it’s invoking a (small) Makefile, so you’d have to dig into that, to find the exact thing which is failing.
You can add ‘-n’ to ‘make’ to see what it calls.
[…] /bin/sh: line 1: 33977 Segmentation fault: 11 /Users/richarddrake/build/TextMate/Frameworks/scm/test_scm
Got another error in trying again so googled and did:
textmate(master) $ ninja scm/coerce
Normally it would fail if you lack ‘hg’ — but missing SCM commands shouldn’t produce segfaults.
textmate(master) $ ninja SoftwareUpdate/coerce [1/1] Skip test '/Users/richarddrake/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate'...
which got me to: [8/26] Run test '/Users/richarddrake/build/TextMate/Frameworks/SoftwareUpdate/test_SoftwareUpdate'...
The SoftwareUpdate/coerce target should cause the test to be skipped, that said, the test is failing because you lack the fixtures, which are missing because ./configure failed.
It’s the first time I hear of someone with ./configure failing to generate the fixtures, so I don’t know what would cause it, but openssl is used in the process, so perhaps you have some non-standard version of that.
Adding ‘-n’ to the make invocation above and then running the commands manually should help track down the problem.
Thanks Allan, that helped get to the bottom of it. I had a stray openssl in my PATH in rbenv shims because (I think) of having installed MagLev Ruby. Having removed it I have a newly compiled version of TM2 opening up - well after one 'ninja scm/coerce'.
Do most people use this edge version for day-to-day work out of interest?
On 15 July 2013 00:42, Allan Odgaard mailinglist@textmate.org wrote:
On 13 Jul 2013, at 14:13, Richard Drake wrote:
textmate(master) $ ./configure
make: *** [/Users/richarddrake/build/**TextMate/Frameworks/** SoftwareUpdate/fixtures/**secret.pem] Error 127
The failing line would be this (which you can try to re-run):
DST=build/Frameworks/**SoftwareUpdate/fixtures make -C Frameworks/SoftwareUpdate/**fixtures
Although it’s invoking a (small) Makefile, so you’d have to dig into that, to find the exact thing which is failing.
You can add ‘-n’ to ‘make’ to see what it calls.
[…]
/bin/sh: line 1: 33977 Segmentation fault: 11 /Users/richarddrake/build/**TextMate/Frameworks/scm/test_**scm
Got another error in trying again so googled and did:
textmate(master) $ ninja scm/coerce
Normally it would fail if you lack ‘hg’ — but missing SCM commands shouldn’t produce segfaults.
textmate(master) $ ninja SoftwareUpdate/coerce
[1/1] Skip test '/Users/richarddrake/build/**TextMate/Frameworks/**SoftwareUpdate/test_** SoftwareUpdate'...
which got me to: [8/26] Run test '/Users/richarddrake/build/**TextMate/Frameworks/**SoftwareUpdate/test_** SoftwareUpdate'...
The SoftwareUpdate/coerce target should cause the test to be skipped, that said, the test is failing because you lack the fixtures, which are missing because ./configure failed.
It’s the first time I hear of someone with ./configure failing to generate the fixtures, so I don’t know what would cause it, but openssl is used in the process, so perhaps you have some non-standard version of that.
Adding ‘-n’ to the make invocation above and then running the commands manually should help track down the problem.
______________________________**_________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/**listinfo/textmatehttp://lists.macromates.com/listinfo/textmate
On 16 Jul 2013, at 0:34, Richard Drake wrote:
[…] Do most people use this edge version for day-to-day work out of interest?
Most people do not do their own build, no. I think it’s something like 86% on normal releases, 13.75% on (the somewhat misnamed) “nightly builds”, and last 0.25% using a custom build (excl. MacPort builds, which are building from a tag, rather than ‘master’).
But the goal is to always have ‘master’ in a good state.
-
Allan Odgaard -
Richard Drake