I found an answer. First off I had to find a distro that was binary compatable. I had to find a version of Centos that had closer versions of the common libraries, if not older than the X-Linux had. After installing Centos version 4 and 3 on two separate VMs, I found Centos 3.9 to be slightly older than the target. In fact it was one rev older on each of the common libraries.
Then I recompiled my code in Centos 3.9 and hoped that it did not rely upon newer features of C++ and such...I lucked out. Then I copied the binaries and libraries over to the target and voila. Working system.
The boss didn't like using a really old version b/c of security fixes etc....so now I have to figure out how to cross compile and create a host/target system, building kernels and the whole nine yards :P.
Main Topics
Browse All Topics





by: e-tsikPosted on 2008-07-01 at 05:54:19ID: 21907248
Hi :-)
m/debian-g cc@lists.d ebian.org/ msg18769.h tml
I know this problem, but from another direction - when I try to ship a glibc along with the executable and redirect the library using LD_LIBRARY_PATH .
tls is threading method introduced by later GCCs. GCC can compile and/or link against the TLS version of glibc or the non-tls version. LD also has to be able to link to the proper version on the other side.
Using CentOS 4, your GCC is 4 . If sending a glibc would not work then you can either make GCC not compile tls code for you (man gcc ?) .
I googled and saw some references to a GCC bug. Here is the one I think is most relevant:
http://www.mail-archive.co
Hope this helps
:-)