Re: Compatibility between Debian amd64 and other distributions
Daniel Jacobowitz <email@example.com> writes:
> On Sat, Sep 23, 2006 at 10:29:37AM +0200, Goswin von Brederlow wrote:
>> Daniel Jacobowitz <firstname.lastname@example.org> writes:
>> > On Sat, Sep 23, 2006 at 02:50:35AM +0200, Goswin von Brederlow wrote:
>> >> But running Debian binaries on other distributions remains a
>> >> problem. For example static binaries that use libnss* plugins will
>> >> fail to find those plugins on other systems. Copying the debian libc6
>> >> to your ~/lib/ dir on another distribution will break locale plugins.
>> > Do you have any less contrived examples? FWIW, I think in either of
>> > these cases you deserve to keep both pieces.
>> How do you keep both pieces if you are not root?
> That has nothing to do with it. Copying libc.so.6 to something other
> than its configured location breaks in plenty of other ways. Static
> binaries using nss are a long-standing and known source of problems,
> and if you copy them to any other version of glibc - configured
> differently or not - you're liable to crash.
So what you seem to say is: If you copy the libc6 or static libraries
between distributions you deserve to fail. Thats fine if you say it
Does the same apply to libX11. Or can we do the compile for lib64, use
lib trick there as it is not frozen?
As for after etch I hope binutils will add the multiarch patch and
then we can finaly start moving stuff there as was planed for after
PS: Should the bug be retitled "Note FHS exception/deviation for amd64
in release notes"?