From: John H. <jd...@gm...> - 2008-06-06 01:50:53
|
On Thu, Jun 5, 2008 at 4:19 PM, Christopher Burns <cb...@be...> wrote: > Is this really the current solution to building matplotlib on OSX, > installing a new compiler and hacking the python Makefile? > > I was able to build matplotlib 0.91.2 just fine on OSX, sometime > around March I checked out the truck to fix a bug and discovered I > couldn't build the svn version. Matplotlib is the only package with a > dependency on gcc 4.2, all the other packages I build, numpy, scipy, > ipython, etc... build with gcc 4.0. Why do you have this dependency? > Is there an easier solution? > > I'm reluctant to upgrade to gcc 4.2 and loose the ability to build > other packages I need. An upgrade to 4.2 is not required. On the svn trunk (0.98) there is a bug in the apple gcc compiler with our agg extension that causes a compiler error if the optimization level is -O3. You can work around it by using -Os instead. I build with the default apple compiler and have a line in the Makefile in the mpl src dir that reads:: build_osx105: CFLAGS="-Os -arch i386 -arch ppc" LDFLAGS="-Os -arch i386 -arch ppc" python setup.py build Some of the other suggested tricks like editing the Python Makefile configs may be handy so you don't have to pass around CFLAGS and LDFLAGS, but they are in no way required. My build notes are at: http://ipython.scipy.org/moin/Py4Science/InstallationOSX but I need to update them with the info in this email. Don't ignore the pkgconfig stuff, as it is helpful to help find freetype and libpng. Here is my build output:: home:~/mpl> rm -rf build home:~/mpl> gcc --version i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465) home:~/mpl> make build_osx105 >& build.out |