[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#277972: glibc: Please change the remaining instances of 'lib64' to 'lib' on amd64

On Sat, Oct 30, 2004 at 04:12:01PM +0200, Andreas Jochens wrote:
> > 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.

You cannot do that if you are not root, while you can extract binaries
out of Debian packages and run them. For simple stuff it works fine.

> 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.

Does the LSB compatibility package for RedHat or Suse provide such a 
symlink ?

> 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?

Yes it works fine for the simple stuff I am interested in (mathematical
command-line driven programs). It is far less trouble than installing
a proper build environment without root access. 


Reply to: