-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Building julia with clang: tests fail #602
Comments
Here's my backtrace, based on Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn). (note that sys0.ji built ok, it's stage1 that failed)
And on Ubuntu clang version 2.9 (tags/RELEASE_29/final) i386-pc-linux-gnu
|
Out of curiosity, I built src/flisp and src/support with gcc, then everything else with clang (on my mac). Somewhat surprisingly (to me at least :), the backtrace was the same in my previous post. |
Now that is fascinating... |
I bet the ubuntu stacktrace will be the same as what I posted or the mac one, if you build flisp and support in debug mode also. Use src/Makefile.debug for that. -viral On 18-Mar-2012, at 10:34 AM, Jameson Nash wrote:
|
We use -std=gnu99 with gcc in Make.inc, which suggests some kind of dependency on a GNU standard. As per clang docs, it also defaults to the gnu99 standard. |
I don't know if it helps, but here's a more complete traceback from my mac:
|
D'oh. |
Compiles fine with clang for me now, but goes into infinite loop in the hashing tests on OS X. Does anyone else see this? Surprisingly, CPU usage is 30% only. I am reopening this - with an updated title. |
Excellent; our infinite loops are efficient :) |
I get everything passing in debug build, and the hashing test segfaults in release build :( |
The debug build completes all the tests successfully. The release build does not. |
Works for me now. |
Building julia with clang segfaults when building sys0.ji. Using OS X 10.7.3, with the clang that ships with XCode 4.3.1 (Apple clang version 3.1 (tags/Apple/clang-318.0.54) (based on LLVM 3.1svn))
The text was updated successfully, but these errors were encountered: