Re: Multiarch in Debian unstable
On Mon, Jun 27, 2011 at 12:16:41PM +0000, Hector Oron wrote:
> 2011/6/27 Török Edwin <firstname.lastname@example.org>:
> > I think gcc already provides a way to find out the multiarch directory,
> > so it should be only a matter of patching gcc.
> Please try not to confuse multiarch with multilibs.
What multilib does is allowing use of incompatible modes of the CPU: 32 bit
vs 64 bit, hard float vs soft float, etc. In Debian non-biarch world, this
is done as separate architectures.
I wonder, is there any reason to not reuse -print-multi-os-directory for
multiarch? Doing that has the benefit of being compatible with all but most
ancient versions of gcc.
Using this option for multiarch wouldn't even break its old use:
(amd64)$ gcc -print-multi-os-directory
(amd64)$ gcc -print-multi-os-directory -m32
Before the conversion of amd64 -m32 to i386, and sparc -m64 to sparc64, it
could keep using biarch paths for the time being but provide the correct
multiarch one when no -m is specified.
Otherwise, it produces oh so useful:
(amd64)$ arm-linux-gnueabi-gcc -print-multi-os-directory
1KB // Microsoft corollary to Hanlon's razor:
// Never attribute to stupidity what can be
// adequately explained by malice.