Closed cyberbryce closed 8 years ago
Hmmmm, this is troubling. I also have had problems installing Julia master
on Homebrew for a while, but I figured I'd let them shake out any problems and worry about it once we hit RC. Of course, we just v0.5.0-rc1
, so I took another look and yes, I get the same thing. I don't have any good leads right now on why however.
This appears to still be a problem.
This should be fixed now! Please brew update
and try again!
Great, with a clean install of the dependencies this seems to have restored brew install julia --HEAD
as an approach to getting master on my machines, so I'll optimistically close the issue. Thanks for this!
(Apologies in advance if, in the course of sitting down to submit this issue several times over a few months and searching for the error code--then getting side-tracked and failing to follow through--I missed an obvious explanation for my recent build failures with Homebrew on the development branch of Julia.)
I've gotten the same 'Error 139' -- which were reported as issues #1 and #43, both of which were essentially unresolved, three or more years ago -- when trying to install the the development version via this tap roughly since April on various recent release and beta versions of both El Capitan or Sierra, on several different Macs of various vintages. I've attempted both clean installs and those with only Homebrew's version of 'cmake' present, always with a clean bill of health for brewing. Sometimes the build fails with a random osxunwind error, but when I get past that, the message and error for the furthest-along build for 'brew install julia --HEAD" is typically a bus error or segmentation fault at precompilation, something like this:
I am presently able to compile the development branch instead (after installing cmake) by following the instructions on the Julia homepage, with just the extra inconvenience of manually linking the binaries and cleaning up, so (a) this should not be seen as an emergency (perhaps especially seeing as nobody else has submitted an issue over this time-frame) and (b) it appears to be something about the build instructions in the tap that suddenly became problematic in the last several months. Most of the tests pass most of the time.
Thanks in advance for any clues.