Bingo!!
Thanks a lot. Indeed, three libraries are loaded:
---------------####################------------------
> open("/lib/libnss_files.so.2", O_RDONLY) = 3
---------------####################------------------
> open("/lib/tls/libc.so.6", O_RDONLY) = 3
---------------####################------------------
> open("/lib/ld-linux.so.2", O_RDONLY) = 3
---------------####################------------------
So this 'static' link is in fact not static at all.
I'll try uClibc.
Thanks again
Mark
On Wed, 2003-12-03 at 22:54, Tzafrir Cohen wrote:
> On Wed, Dec 03, 2003 at 12:37:48PM +0200, Mark Silberstein wrote:
> > Hi all,
> > can anyone explain, why statically linked binaries from glibc2.2 systems
> > segfault on glibc2.3 systems? If the link is static, doesn't it mean
> > that binary compatibility between the systems is sufficient to run the
> > executable?
> > Mark
>
> strace them. I recall somethingregarding a different nsswitch
> interface (/lib/nss* ) which is loaded via ldopen after readin
> /etc/nsswitch. I believe that this is why /bin/rpm is not statically
> linked on RH9.
>
> For one specific use I was able to get away with using a different libc
> altogether (uClibc for producing the ultimatly static busybox)
--------------------------------------------------------------------------
Haifa Linux Club Mailing List (http://www.haifux.org)
To unsub send an empty message to [EMAIL PROTECTED]
