Comment 11 for bug 783155

Revision history for this message
Peter Funk (pf-artcom-gmbh) wrote : Re: [Bug 783155] Re: Natty: Loader chooses 64-bit instead of 32-bit library

Hello,

> Same problem for me with the 32bit game installer that use Gtk.
> My ugly fix was to temporarily link /usr/lib to lib32 :-(

There is one thing I never understood:

The 64-Bit Debian and Ubuntu distribution flavors store
64-Bit libraries in /lib, /usr/lib ... and 32-Bit
libraries in /lib, /usr/lib32 ...

However the SuSE Linux (now Novell) 64-Bit Linux distros stores the
64-Bit libraries underneath /lib64, /usr/lib64, ... and keep 32-Bit
libraries under the default paths /lib, /usr/lib ...

see:
 +------- SUSE Linux Enterprise Server 11 (x86_64): ----------------
 | $ uname -m
 | x86_64
 | $ file /lib/libc-2.11.1.so
 | /lib/libc-2.11.1.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), not stripped
 | $ file /lib64/libc-2.11.1.so
 | /lib64/libc-2.11.1.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), not stripped

In my experience within the SuSE community there are lot less
complaints about compatibility problems with x86 legacy applications.

What is the reason for this difference between 64-Bit Linux
distributions?

Best Regards, Peter.