Skip to content
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

_macosx.so crash in build using Xcode 5 #2451

Closed
fonnesbeck opened this issue Sep 23, 2013 · 13 comments
Closed

_macosx.so crash in build using Xcode 5 #2451

fonnesbeck opened this issue Sep 23, 2013 · 13 comments
Milestone

Comments

@fonnesbeck
Copy link

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.

@dmcdougall
Copy link
Member

Looks like you're building from master. Are you able to successfully build v1.3 with Xcode 5?

@fonnesbeck
Copy link
Author

I get a different error when running a build of 1.3:

ImportError: cannot import name _string_to_bool

This occurs when pylab is imported.

@fonnesbeck
Copy link
Author

OK, I got a build to work using the 1.3 release. No crash.

@dmcdougall
Copy link
Member

Thanks for the diagnostic information. This is probably related to the migration from 2to3 to six (the relevant commit is f4adec7), but I could be wrong. As a test, would you mind seeing if you are able to successfully build with Xcode 5 using the patch in #2433? If so, I'll close this issue. If not, then that means there's something funky going on.

@fonnesbeck
Copy link
Author

This patch does not fix the issue. Same behavior results.

@mdboom
Copy link
Member

mdboom commented Sep 24, 2013

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).

@fonnesbeck
Copy link
Author

Any plotting will cause the failure. This does it for me every time:

import matplotlib.pyplot as plt
plt.plot(range(10))

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.

@mdboom
Copy link
Member

mdboom commented Sep 30, 2013

Make sure you remove the build directory before rebuilding to ensure a complete rebuild of the C++ code.

@fonnesbeck
Copy link
Author

This is automated in my build script, so that is not the issue.

@tacaswell
Copy link
Member

@fonnesbeck Is this still an issue?

@matthew-brett Do you build with a version of xcode?

@tacaswell tacaswell added this to the v1.4.x milestone Aug 17, 2014
@matthew-brett
Copy link
Contributor

Yes - I build with the latest xcode - so I guess this isn't an issue.
The build logs from matplotlib-wheels give the full output if anyone
wants to check.

@tacaswell
Copy link
Member

I am going to close this then.

@fonnesbeck ping to have this re-opened if you still have issues.

@pelson
Copy link
Member

pelson commented Sep 30, 2014

FWIW, whenever I get this, it is because I have old .pyc files in my source checkout. We moved axes.py to axes/__init__.py and any lingering pyc files can get really messed up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants