On 06/12/2010 03:34 AM, Georg S. Weber wrote: >> >>> I mean what will happen on OS X? >> >> I have pkg-config installed automatically via MacPorts, so at least some >> OSX systems will have the program. In the case of matplotlib, it looks >> like it has a fallback (which is taken care of in the patches in the >> update spkg) >> >> Thanks, >> >> Jason > > If one wants to build Sage under Mac OS, currently it is advised to > move MacPorts/Fink "out of the way", e.g. by renaming the paths (/ > opt/... and /sw/...), and for good reason --- there have been too many > problems in the past. So relying on a program from there is not a way > to go at the time being.
In my case, the problem was that the macports pkg-config was picking up the system (i.e., macports) version of freetype2, since we weren't setting the PKG_CONFIG_PATH variable. Once we set that to point to the local Sage pkg-config directory (SAGE_ROOT/local/lib/pkgconfig), matplotlib used pkg-config to correctly pick up the local Sage installation of freetype. So I wonder if that is the root of our macports problems! If so, then #9208 is a good fix.
In my case, I usually build Sage and then move the directory. This invalidates the paths in the Sage pkgconfig files. So #9210 fixes that by originally rewriting the SAGE_ROOT paths in pkgconfig to use a SAGE_ROOT variable, and then every time Sage is moved, the SAGE_ROOT variable is updated. That seems to work for me (famous last words, I know!). The patch is up at #9210 and ready for review (David has been working on reviewing it, for example).
Thanks, Jason -- Jason Grout -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
