Hang on, this gets a little complicated...
I'm having some difficulty using a shared library that
my program (python actually) is trying to load dynamically at run time.
The problem seems to stem from the fact that my shared library
uses "long long" data variables and does some math with them.
I notice that there are undefined references to the following functions:
__divdi3, __muldi3, __floatdidf, __moddi3
from my shared library.
These routines are not present in any of the /usr/lib/*.so files.
In fact, they are located in the libgcc.a that is part of the gcc installation.
Problem is, I guess, that when I create my shared library, the
libgcc routines don't get linked in, and somehow they are also
omitted from the link of the program (python) since it probably
dosen't use any "long long" stuff.
The relevant components here are python-1.4 and my shared library,
both built with gcc-126.96.36.199, all running on solaris 2.5.1.
What I was able to do, for an immediate work around, was to add the
someplace in the main routine for the program (python) that eventually
tries to load my shared lib. This in fact works, and the resulting
python can load my shared lib (as part of an extension module) and
it works real well.
But, I'd rather find some solution where a standard, unmodified python
executeable is able to load my shared library.
Any tips would be greatly appreciated.