-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build fail using --HEAD #61
Comments
I ran into this problem yesterday as well; thank you for reporting, I'll document my progress here. |
I have been experiencing a similar problem, however the error message is different:
Initially, I thought the problem had to do with some lock files already existing in my cache, which was complained about in the log: http://cl.ly/Tdzy/julia_log.txt The problem persisted after I had removed Homebrew's cache folder from my system using rm -rf $(brew --cache). The log of this failed attempt may be found at http://cl.ly/TdkY/julia_log2.txt |
Yes, I believe this is the same root cause. We recently changed up how On Thu, Jan 30, 2014 at 1:51 AM, dajero [email protected] wrote:
|
Actually, I think I've managed to institute a fix, please clear your cached julia .git folders (a Note that I am running into segfaults during build that I haven't figured out yet. They don't happen outside of Homebrew, so I'm pretty sure I'm screwing something up somewhere. |
Elliot's fix has worked for me over several updates now. Not hearing otherwise I'll tentatively close this. |
The 0.2 release installs correctly, but I ran into this failure compiling the prerelease version of julia using --HEAD. I upgraded homebrew and reinstalled gfortran and the other dependencies, and tried it with --64bit and without. These changes had no effect; it looks like the error is related to the documentation:
Cloning into 'doc/juliadoc'...
Checking connectivity... done
Submodule path 'doc/juliadoc': checked out '300b72cd13fe9b54b938a0b49416e4d860181d0f'
make[1]: *** [julia-release] Error 2
make: *** [release] Error 2
I worry that it leads to endless headaches to install prereleases right before a new release, but I do find some of the changes since 0.2 to be important to my project.
The text was updated successfully, but these errors were encountered: