On May 10, 10:36 am, Prabhu Ramachandran <pra...@aero.iitb.ac.in> wrote: > On 05/10/09 21:58, mabshoff wrote:
Hi Prabhu, <SNIP> > Well, I have seen this when I got the error first time (google is our > friend) but didn't believe the answer would work for the simple reason > that VTK is really well tested. I didn't want to mess with compilation > arguments before testing other options. Regardless, I did try a manual > link with -Wl,-single_module and it didn't work -- I got different > errors. I could try -fno-common but that would have to be done for the > Python build and not the VTK build. It appears that the problem is not > with VTK but the Python build since the linking fails for the Python > library. The VTK libraries are linked to each other quite nicely. Ok. I would still consider this strange, but IIRC most python builds on OSX are Framework builds. Adding some custom flags like -fno-common and/or -fPIC wouldn't be a problem for Sage IMHO. I am aware of some other problems with for example dyanmic python libraries with modern toolchains on Linux since they do require -fPIC. This problem seems to be unresolved in Python 2.5, but I think something has been done about this in Python 2.6. > >> I guess I could retry with a non-framework build but it really takes a > >> while to build on my machine and all previous attempts failed. > > > Sure. Let me know if the above works. > > I've tried the above and a few other things too. I'm still all ears > though, so keep the suggestions coming. Well, I would need to play around with VTK, but I don't really have the time to do that now :(. <SNIP> > > Well, it doesn't matter for builds from source too much, the real > > problem is when a user runs -upgrade for Sage. > > Sorry for being dense. You mean when the user runs -upgrade with a > non-framework install? Suppose a user has a fresh install, would the > framework build cause problems when this user does a -upgrade? > IOW, is this only a problem for those with older non-framework builds? Sorry, I wasn't quite correct - at least I wanted to write something else: When you build python as framework without ever having build it as non-framework there are some problems. They are fixable, but so far I have not been convinced that building the Python in Sage as a framework solves more problems that it causes. > Thanks. > > cheers, > prabhu Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
