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

Re: AMD64 and lib64

On Wed, 7 Jul 2004, Martin Michlmayr - Debian Project Leader wrote:

> * Tollef Fog Heen <tfheen@raw.no> [2004-07-07 13:43]:
> > lib64 is ugly and wrong, wrong, wrong.
> But it's in LSB which Debian wants to follow...
> > You were at the multiarch talk during debconf4, and that is, IMO,
> > the sane way to do it.
> ... and multiarch is far away.

About as far away as patching everything to use /lib64 really.

Well, perhaps multiarch is a bit more work, but first patching for /lib64
and then reverting for multiarch is a significant effort better spent on
getting multiarch up and running.

> > We don't do that.  At least not for the current AMD64 port.  It's a pure
> > 64 bit port without any 32 bit compatibility.  The way to do multiarch
> What about people who need 32 bit compatibility?

Install the package ia32-libs and perhaps tinker a little bit. This works
with the pathscale compiler suite which is a fairly large and
non-trivial ia32 package.

This won't be LSB IA32 compliant, but it should be a workable solution for
those needing that for commercial packages etc.

> > | For binary compatability reasons with other distributions you should
> > | be also careful that all of the application binaries refer to /lib64
> > | rather than /lib.
> >
> > We are aware of that, and /lib64 is a symlink for the time being.
> This doesn't help when someone wants to run Debian binaries on another
> architecture.  Does Debian want to be perceived as incompatible with
> the rest of the world?

This might be an issue though.

/Mattias Wadenstein

Reply to: