On Friday 02 June 2006 16:59, Robert Schiele wrote:
On Wed, May 31, 2006 at 10:34:34AM +0200, Bernd Paysan wrote:
However, ld-linux.so can run programs directly, so that might be an option to copy the old ld-linux.so into the Cadence lib directory and call the offending program using that ld-linux.so. But even using that I get the same error message, since the first process spawns further, which refer again to /lib/ld-linux.so.2:
/cad/cds_ic_v5.0.33_usr3/tools/bin/clsbd: relocation error: /cad/cds_ic_v5.0.33_usr3/tools/lib/libc.so.6: symbol _dl_out_of_memory, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference
Then you most likely did something wrong. Since you did not tell us how exactly you called the linker I cannot tell you what.
With /<path-to-old-libraries>/ld-linux.so /<path-to-cadence>/icfb.exe. I have LD_LIBRARY_PATH set appropriate.
I once built a tool that automatically generates self-contained packages like http://db.informatik.uni-mannheim.de/downloads/natix/natix-2.1.0.tar.bz2 from a set of RPM packages and never saw any problems with these packages on any system.
Do your programs exec() other programs with the same problems? Cadence does, and that's the problem. Apparently, there is no way to tell the Linux kernel that it should use another ld.so instead of /lib/ld-linux.so other than chroot - and chrooting just one specific X application is fairly difficult. -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/