Nope. ranlib run on each of the libraries being complained about has no
effect whatsoever on the problem. Guido said I should look into the way the
libraries are being ordered and it changed the symbols that were being
complained about. I think it might help me to know exactly how extensions
are integrated with the main package, link wise not source wise :-)
I have only had the package for a few hours but I think the vanilla
intepreter is encapsulated in libModule.a libObject.a libParser.a
libPython.a in addition to a few other libraries like readline etc. To add
an extension, does one simply link in the extension.o file and the lib.a
generating in the compilation of the extension ? If so I could hack the
main python generation to just include those libraries in its link step.
On a general note, I just can't understand how ld could not resolve all the
symbols if all the libraries needed are present. Thats its whole purpose. I
still think I'm missing something basic. Or not. If the install script
seems to work for everyone else but not for me it must be my fault :-)
-- Guido > Sam >-- >"La cervelle des petits enfants, ca doit avoir comme un petit gout de noisette" > Charles Baudelaire