Bug#277972: glibc: Please change the remaining instances of 'lib64' to 'lib' on amd64
On 04-Oct-30 15:36, Bill Allombert wrote:
> On Mon, Oct 25, 2004 at 08:18:40AM +0200, Andreas Jochens wrote:
> > I patched the gcc-3.4 package in the amd64/gcc-3.4 archive to get that
> > result. For the patch I used please look at BTS #277852. I recompiled
> > the complete amd64/gcc-3.4 archive with that patch and without the
> > '/lib64' and '/usr/lib64' symlinks in place. I still have to reupload
> > most of the recompiled packages to alioth but you should be able to
> > debootstrap a new chroot from the amd64/gcc-3.4 archive and do a
> > 'rm /lib64' without making the system unusable.
>
> Does your binaries run on other x86-64 distributions without any compat
> symlinks ? I think this is an absolute requirement for pure64.
The binaries will run on all distributions which have
the interpreter accessible as /lib/ld-linux-x86-64.so.2.
Gentoo, Ubuntu and of course pure64 install the interpreter as
/lib/ld-linux-x86-64.so.2 today, so the binaries will run on these
distributions without changes. On other distributions it may
be necessary to execute
ln -sf /lib64/ld-linux-x86-64.so.2 /lib/ld-linux-x86-64.so.2
to run the binaries until those distributions install that symlink
themselves.
Anyway, if you intend to run binaries on different distributions,
you should create binaries which conform to the LSB standard and you
should install the LSB compatibility package on the target
system. Otherwise you will certainly have more serious problems
than the location of the interpreter.
Regards
Andreas Jochens
P.S.: Do you really want to install Debian binary packages on
other (non-Debian related) distributions (e.g. RedHat, SuSe)?
Have you already tried that and did it work?
Reply to: