adonthell-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Adonthell-devel] New code base released!


From: Kai Sterker
Subject: Re: [Adonthell-devel] New code base released!
Date: Fri, 20 Jun 2003 00:48:38 +0200

Am Freitag, 20.06.03 um 00:28 Uhr schrieb Kai Sterker:

It's the linking that fails, like with the first 0.4 test, only a bit different this time (see attachment).

Seems that a lot of lt_* stuff is defined in multiple libs/object files (whatever). Namely libadonthell_gfx.0.0.0.dylib-master.o and libadonthell_base.0.0.0.dylib-master.o. But see for yourself.

Well, removing the $(LIBLTDL) from src/base/Makefile.am resolved that problem. However, a bit later I ran into trouble with our python.h and Python's Python.h. Changing the include from "Python.h" to <Python.h> in src/python/python.h fixed that too. Still the linking of the python module fails with more weird errors:

Making all in python
/bin/sh ../../libtool --mode=link g++ -g -Wall -fno-exceptions -fno-rtti -I../../src/ -o libadonthell_python.la -rpath /usr/local/lib libadonthell_python_la-python.lo libadonthell_python_la-callback.lo -L/usr/lib/python2.2/config -lpython2.2 -L../base -ladonthell_base -L../../libswigruntime -lswigruntime -lstdc++ -lz rm -fr .libs/libadonthell_python.la .libs/libadonthell_python.* .libs/libadonthell_python.* g++ -r -keep_private_externs -nostdlib -o .libs/libadonthell_python.0.0.0.dylib-master.o libadonthell_python_la-python.lo libadonthell_python_la-callback.lo && gcc -dynamiclib -flat_namespace -undefined suppress -o .libs/libadonthell_python.0.0.0.dylib .libs/libadonthell_python.0.0.0.dylib-master.o -L/usr/lib/python2.2/config -lpython2.2 -L/Users/kai/adonthell/adonthell-0.4dev1/src/base -L/Users/kai/adonthell/adonthell-0.4dev1/src/base/.libs -ladonthell_base -L/Users/kai/adonthell/adonthell-0.4dev1/libswigruntime -L/Users/kai/adonthell/adonthell-0.4dev1/libswigruntime/.libs -lswigruntime -lstdc++ -lz -lc -install_name /usr/local/lib/libadonthell_python.0.dylib -compatibility_version 1 -current_version 1.0 ld: common symbols not allowed with MH_DYLIB output format with the -multi_module option /usr/lib/python2.2/config/libpython2.2.a(exceptions.o) definition of common _PyExc_Exception (size 4) /usr/lib/python2.2/config/libpython2.2.a(exceptions.o) definition of common _PyExc_MemoryError (size 4)
[...]

Note the "ld: common symbols not allowed with MH_DYLIB output format with the -multi_module option". Either that is an option which is enable by default and must be disabled with some switch, or whatever. I see if I can work around it somehow, though.

But not today, as it is getting late. Maybe tomorrow evening, or when I need a brake from Java during the day ;).

Kai





reply via email to

[Prev in Thread] Current Thread [Next in Thread]