public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: multilib and the compatibility to singlelib
Date: Tue, 20 Oct 2009 14:16:01 -0400	[thread overview]
Message-ID: <200910201416.02169.vapier@gentoo.org> (raw)
In-Reply-To: <4ADDB5D5.30502@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 2135 bytes --]

On Tuesday 20 October 2009 09:06:29 Michael Haubenwallner wrote:
> As I'm building the toolchain myself too, I configure it with the
> 32bit host triplet on each platform, usually disabling multilib.

this doesnt make any sense to me

> This simply works for ppc-aix, hppa-hpux, ia64-hpux, sparc-solaris,
> x86-solaris, even if the underlying OS/kernel is 64bit.
> It isn't even necessary to explicitly use --{build,host} at all,
> as config.guess tells the 32bit triplet on these platforms.
> Additionally, even their default compiler output is 32bit.
> 
> But Linux "is not Unix":

you're right, so i'm not terribly concerned with compatibility with non-Linux 
systems.  comparing the native Gentoo/Linux multilib setup to another Linux 
multilib setup is the only useful comparison.

> Configuring both binutils and gcc needs to be done with:
>   $ CC="gcc -m32" /path/to/configure --{build,host}=i686-pc-linux-gnu ...
> This works on 64bit RHEL as well as on 64bit SLES (both have 32bit in /lib,
> 64bit in /lib64, no /lib32), but breaks on amd64+multilib Gentoo Linux.
> 
> Problem is that, as x86-linux isn't a multilib target, both ld and gcc
> search for 32bit libs&objects in /usr/lib:/lib, as they don't know about
> /usr/lib32:/lib32. The error when bootstrapping gcc is:
>   /usr/lib/crti.o: file not recognized: File format not recognized

i dont get it.  why does the i686-pc-linux-gnu toolchain target matter on an 
amd64 multilib system ?  the native x86_64-pc-linux-gnu toolchain should 
already do the right thing when given -m32.

> While it is possible to patch binutils[1] and gcc[2] to search in
> /usr/lib32:/lib32 even with this otherways non-multilib target,
> it doesn't feel like the "right thing" to enable multilib for
> just one multilib option.
> 
> Isn't the intention of multilib to have a new (64bit) system
> be compatible with the corresponding old (32bit) system?

your description of "compatible" is pretty vague.  ignoring /lib -> /lib64 
symlink (which shouldnt matter to any binaries), i'm not aware of any 
differences off the top of my head.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2009-10-20 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 13:06 [gentoo-dev] RFC: multilib and the compatibility to singlelib Michael Haubenwallner
2009-10-20 14:19 ` [gentoo-dev] " Nikos Chantziaras
2009-10-20 15:29 ` [gentoo-dev] " Thomas Sachau
2009-10-20 16:25   ` [gentoo-dev] " Duncan
2009-10-20 17:45     ` Mike Frysinger
2009-10-20 20:47       ` Jonathan Callen
2009-10-21  1:27         ` Mike Frysinger
2009-10-20 18:16 ` Mike Frysinger [this message]
2009-10-21 11:34   ` [gentoo-dev] " Michael Haubenwallner
2009-10-26 12:12     ` Mike Frysinger
2009-10-27 10:19       ` Michael Haubenwallner

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=200910201416.02169.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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