2010/8/10 Derek Homeier <de...@astro.physik.uni-goettingen.de>: > Hi again, cc'ing the matplotlib list this time, > > for the latter: when building matplotlib against a fink-installed python > compiled in 64bit mode > I found the check for a framework-installed Python (rev 8365) fails, and > matplotlib fails to load, > because the MacOS module is not available in 64bit.
Hmm, do you claim that MacOS is in general not available in x86_64? Just my 2 cents: pb-d-128-141-26-145:~ Friedrich$ python-32 Python 2.6.5 (r265:79063, Jul 18 2010, 12:14:53) [GCC 4.2.1 (Apple Inc. build 5659)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import MacOS >>> ^D pb-d-128-141-26-145:~ Friedrich$ python-64 Python 2.6.5 (r265:79063, Jul 18 2010, 12:14:53) [GCC 4.2.1 (Apple Inc. build 5659)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import MacOS >>> ^D This is a self-compiled python.org Python 2.6.5 residing in /Library/Frameworks/Python.framwork: ./configure --enable-framework --with-universal-archs=intel --enable-universalsdk=/ with MACOSX_DEPLOYMENT_TARGET=10.4 GCC=gcc-4.2 Please bear with me, but how does framework/not-framework interfere with the build of the MacOS module? > (assuming Python is not a framework installation if it lacks the MacOS > module). Are there more implications? I always thought framework build just means to put it in /Library/Framworks/Python.framework. Friedrich ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
