I was on Mavericks this morning, attempting to compile TextMate (latest git HEAD) But I suspect its no longer possible since it appears to require a more recent version of XCode - error in one function due to 'forced copy in constructor'. It was related to a parents = {} parameter, I didn't dig too deeply.
Not to worry, it gave me a good reason to upgrade to El Capitan. So I've done that, and updated all the homebrew packages, aswell as Xcode The github states that hg (mercurial) is optional, but I installed it anyway to allow the unit tests to run.
Unfortunately I'm still having problems
----- environment
[carpii@imac:~/dev/textmate]$ clang++ --version Apple LLVM version 7.3.0 (clang-703.0.31) Target: x86_64-apple-darwin15.5.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
[carpii@imac:~/dev/textmate]$ clang --version Apple LLVM version 7.3.0 (clang-703.0.31) Target: x86_64-apple-darwin15.5.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
[carpii@imac:~/dev/textmate]$ xcodebuild -version Xcode 7.3.1 Build version 7D1014
[carpii@imac:~/dev/textmate]$ sw_vers -productVersion 10.11.5
------- compilation
[carpii@imac:~/dev/textmate]$ ninja -t clean Cleaning... 515 files.
[carpii@imac:~/dev/textmate]$ ninja io [1/1] Generate ‘build.ninja’… [109/109] Run test ‘/Users/carpii/build/TextMate/Frameworks/io/test_io’…
[carpii@imac:~/dev/textmate]$ ninja TextMate [229/1107] Run test ‘/Users/carpii/build/TextMate/Frameworks/scm/test_scm’… FAILED: /Users/carpii/build/TextMate/Frameworks/scm/test_scm && touch /Users/carpii/build/TextMate/Frameworks/scm/test_scm.run /bin/sh: line 1: 7210 Segmentation fault: 11 /Users/carpii/build/TextMate/Frameworks/scm/test_scm [229/1107] Compile ‘Frameworks/file/src/open.cc’… ninja: build stopped: subcommand failed.
Any ideas please?
On Tue, Jun 14, 2016 at 2:06 PM, Carpii UK carpii.uk@gmail.com wrote:
I was on Mavericks this morning, attempting to compile TextMate (latest git HEAD) But I suspect its no longer possible since it appears to require a more recent version of XCode - error in one function due to 'forced copy in constructor'. It was related to a parents = {} parameter, I didn't dig too deeply.
Not to worry, it gave me a good reason to upgrade to El Capitan. So I've done that, and updated all the homebrew packages, aswell as Xcode The github states that hg (mercurial) is optional, but I installed it anyway to allow the unit tests to run.
Unfortunately I'm still having problems
Any ideas please?
See https://github.com/textmate/textmate/pull/1325
Ron
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
See https://github.com/textmate/textmate/pull/1325
Ron
Thankyou! that fixed the scm tests.
I don't suppose you also faced this issue?
[335/528] Run test ‘/Users/carpii/build/TextMate/Frameworks/document/test_document’… FAILED: /Users/carpii/build/TextMate/Frameworks/document/test_document && touch /Users/carpii/build/TextMate/Frameworks/document/test_document.run libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument /bin/sh: line 1: 10913 Abort trap: 6 /Users/carpii/build/TextMate/Frameworks/document/test_document
That happens when you have TM open sometimes when compiling. Just close it and it should work.
On 14 Jun 2016, at 20:21, Carpii UK wrote:
Thankyou! that fixed the scm tests.
I don't suppose you also faced this issue?
[335/528] Run test ‘/Users/carpii/build/TextMate/Frameworks/document/test_document’… FAILED: /Users/carpii/build/TextMate/Frameworks/document/test_document && touch /Users/carpii/build/TextMate/Frameworks/document/test_document.run
This one currently also fails for me (most of the time), you can skip it by running:
touch /Users/carpii/build/TextMate/Frameworks/document/test_document.run
I’m currently doing major refactoring on the document framework, I don’t think this has actually broken anything though the tests are multi-threaded so it is most likely a race condition related to this (there are some issues I am aware of here that may be exercised by the tests but which should not happen in practice, and which should be gone once my refactoring work is done).
Thanks all, managed to bypass the failing test.
All compiled and linked now :)
On 14 June 2016 at 19:27, Allan Odgaard mailinglist@textmate.org wrote:
On 14 Jun 2016, at 20:21, Carpii UK wrote:
Thankyou! that fixed the scm tests.
I don't suppose you also faced this issue?
[335/528] Run test ‘/Users/carpii/build/TextMate/Frameworks/document/test_document’… FAILED: /Users/carpii/build/TextMate/Frameworks/document/test_document && touch /Users/carpii/build/TextMate/Frameworks/document/test_document.run
This one currently also fails for me (most of the time), you can skip it by running:
touch/Users/carpii/build/TextMate/Frameworks/document/test_document.run
I’m currently doing major refactoring on the document framework, I don’t think this has actually broken anything though the tests are multi-threaded so it is most likely a race condition related to this (there are some issues I am aware of here that may be exercised by the tests but which should not happen in practice, and which should be gone once my refactoring work is done).
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 14 Jun 2016, at 20:27, Allan Odgaard wrote:
[335/528] Run test ‘/Users/carpii/build/TextMate/Frameworks/document/test_document’… FAILED: /Users/carpii/build/TextMate/Frameworks/document/test_document && touch /Users/carpii/build/TextMate/Frameworks/document/test_document.run
This one currently also fails for me […]
Just a small update to let people know that tests should no longer fail.
Code executed from tests no longer make use of the main dispatch queue which seems to have fixed the problem, instead they use the caller’s thread (via CFRunLoopPerformBlock).
-
Allan Odgaard -
Carpii UK -
Josh Bernitt -
Ronald Wampler