[Starkit] Big Hole in Foot.
jahbini at lava.net
Sat Jun 12 18:02:13 CEST 2004
I have been using tclkit technology to wrap a large distributed
application. The idea is that it unwraps on each of four different
processors and configures itself to behave differently on each
different machine, depending on the host name.
The system is to control an astronomical instrument, move
filter-wheels, start exposures, grab images, send them to remote data
handling systems, etc.
Much of this depends on shared libraries that are supplied to me (not
negotiable) but I can embed them into my bigAssApplication.kit.
This has worked well and I'm pretty much married to this architecture
and technology. The ease of wrapping and sending the
bigAssApplication.kit to the separate systems has proven valuable.
I have had to adapt the base tclkit to a modified notATclkit that
includes, among other things, the thread library 'libpthread.so' and
C++ library 'libstdc++.so'
OK. Now the rub. Testing on some systems (previous linux distros) has
failed because the libraries, libpthread.so and libstdc.so are PRIOR
versions to the ones on my development system. And the notATclkit
can't load and execute without them.
Do I need to compile my notATclkit on EACH possible linux distro? Or
is there a way to force the linux loader to include the libpthread.so
from MY development system into the executable (notATclkit)? I have
RTFM most amazingly and have brain fatigue at the third level of
binutil hell and tried every command line option to 'ld' but still have
not found if this is possible.
It's now time to ask the big boys if there is a way to perform this
Thanks for your flames, they will help cauterize the big hole I have
put in my foot.
More information about the Starkit