On May 10, 9:19 am, Prabhu Ramachandran <pra...@aero.iitb.ac.in>
wrote:
> On 05/10/09 21:03, mabshoff wrote:

Hi Prabhu,

> > I don't understand why VTK needs Python to be a framework. Googling
> > around for 5 minutes did not reveal anything useful. Can you give me
> > some pointers and/or documentation on this?
>
> I really don't know if this is needed or not.  It could well be a VTK
> issue.  I need to build VTK with Carbon support and I'm not sure that
> requires a framework build of Python. Anyway, VTK tries to detect the
> Python library to link to when it builds the Python wrappers.  I think
> it finds the system Python by default which obviously will not work.
> When I point it to the libpython25.a file in
> SAGE_LOCAL/lib/python2.5/config, I get link errors since my guess is
> that file is not a proper universal library?  Upon some digging,
> fortunately, I seem to have an install.log lying around.  Here is the
> exact error message I got when linking to libpython25.a:
>
> Linking CXX shared library ../bin/libvtkCommonPythonD.dylib
>
> ld: common symbols not allowed with MH_DYLIB output format with the
> -multi_module option

<SNIP>

Ok, check out

 http://www.mail-archive.com/g...@gcc.gnu.org/msg05799.html

for a probable solution. It might then expose the next issue, but I
guess this is step by step ;).

> If I leave the Python library unspecified it runs into linker errors
> with symbols being undefined at link time.  None of this happens with a
> framework build.
>
> 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.

> > Another problem is that if we changed the default for OSX we would
> > need to force a rebuild of every other python component in Sage, so
> > since we don't have any problems as it is seems plainly not worth it.
>
> But isn't everything anyways built from source?  So how would this
> affect anything? In my case nothing else seems affected -- I rebuilt
> Python and installed that over the existing build. I didn't test too
> much apart from VTK related scripts though.

Well, it doesn't matter for builds from source too much, the real
problem is when a user runs -upgrade for Sage.

> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to