From: Stefan Smietanowski <stesmi@stesmi.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Andi Kleen <ak@suse.de>, Jim Gifford <maillist@jg555.com>,
linux-kernel@vger.kernel.org
Subject: Re: Pure 64 bootloaders
Date: Sun, 11 Sep 2005 16:14:52 +0200 [thread overview]
Message-ID: <43243BDC.7020309@stesmi.com> (raw)
In-Reply-To: <20050911115327.GZ6026@ns.snowman.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi.
>>Jim Gifford <maillist@jg555.com> writes:
>>
>>>I have been working on a project to create a Pure 64 bit distro of
>>>linux, nothing 32 bit in the system. I can accomplish that with no
>>
>>Hopefully you're using /lib64 for that, otherwise your
>>packages will be incompatible to everybody else and not
>>FHS compliant. If you don't please don't submit any
>>patches to hardcode this to upstream packages.
>
>
> /lib64 sucks, as mentioned, and I thought FHS only required that the
> linker be in /lib64. Thus, the actual libraries could be pretty much
> anywhere (as it should be, really). Debian-amd64 uses a symlink from
> /lib64 to /lib and provides the 64bit libraries and linker in /lib (but
> when actually compiling does link binaries through /lib64 for FHS
> compliance).
>
> Hopefully /lib64, et al, will die and multiarch will happen soon.
How exactly would multiarch support work then?
// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFDJDvcBrn2kJu9P78RAk9/AJ9KkdDxnqQmRSonntRZBqONlMH2pgCfQpH/
FDhtQSwqDrBzrQUb6/5YeOs=
=fEv6
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2005-09-11 14:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 7:42 Pure 64 bootloaders Jim Gifford
2005-09-10 7:52 ` Jeff Garzik
2005-09-10 8:01 ` David S. Miller
2005-09-11 16:33 ` Jim Gifford
2005-09-11 18:48 ` David S. Miller
2005-09-11 18:49 ` David S. Miller
2005-09-10 8:28 ` Andi Kleen
2005-09-10 8:39 ` Jeff Garzik
2005-09-10 16:34 ` Chris Wedgwood
2005-09-10 18:15 ` David S. Miller
2005-09-12 21:32 ` Joe Bob Spamtest
2005-09-12 21:41 ` David S. Miller
2005-09-12 22:02 ` Joe Bob Spamtest
2005-09-12 22:12 ` David S. Miller
2005-09-12 23:09 ` Joe Bob Spamtest
2005-09-13 16:52 ` Lennart Sorensen
2005-09-13 17:00 ` Joe Bob Spamtest
2005-09-14 3:44 ` Kyle Moffett
2005-09-14 13:20 ` Lennart Sorensen
2005-09-14 17:26 ` Kyle Moffett
2005-09-13 17:21 ` Maciej W. Rozycki
2005-09-13 19:37 ` Lennart Sorensen
2005-09-14 9:39 ` Maciej W. Rozycki
2005-09-10 18:30 ` Harald Dunkel
2005-09-12 14:50 ` Roger Heflin
2005-09-13 17:14 ` Bastian Blank
2005-09-15 6:16 ` Harald Dunkel
2005-09-11 11:53 ` Stephen Frost
2005-09-11 14:14 ` Stefan Smietanowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43243BDC.7020309@stesmi.com \
--to=stesmi@stesmi.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maillist@jg555.com \
--cc=sfrost@snowman.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox