-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
_macosx.so crash in build using Xcode 5 #2451
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
Comments
Looks like you're building from |
I get a different error when running a build of 1.3:
This occurs when pylab is imported. |
OK, I got a build to work using the 1.3 release. No crash. |
Thanks for the diagnostic information. This is probably related to the migration from |
This patch does not fix the issue. Same behavior results. |
Can you provide a full script that reproduces the error? (Or point to one of our examples that fails?) I'm unable to reproduce (once #2433 is applied, now merged to master). |
Any plotting will cause the failure. This does it for me every time:
If I roll back to the 1.3 release, the problem disappears. I will try again from master incase I made a mistake in testing the patch. |
Make sure you remove the build directory before rebuilding to ensure a complete rebuild of the C++ code. |
This is automated in my build script, so that is not the issue. |
@fonnesbeck Is this still an issue? @matthew-brett Do you build with a version of xcode? |
Yes - I build with the latest xcode - so I guess this isn't an issue. |
I am going to close this then. @fonnesbeck ping to have this re-opened if you still have issues. |
FWIW, whenever I get this, it is because I have old |
After upgrading to Xcode 5 on OS X 10.8.4, matplotlib is no longer able to use the macosx backend without crashing.
Here is the crash report from one such crash.
This is a build for the ScipySuperpack, so I am using a script that has successfully built working packages every 2 weeks or so until now. I also tried using the instructions in
README.osx
, with the same result.The text was updated successfully, but these errors were encountered: