Gentoo Logo
Gentoo Spaceship

Installation:
Gentoo Handbook
Installation Docs

Documentation:
Home
Listing
About Gentoo
Philosophy
Social Contract

Resources:
Bug Tracker
Developer List
Discussion Forums
Gentoo BitTorrents
Gentoo Linux Enhancement Proposals
IRC Channels
Mailing Lists
Mirrors
Name and Logo Guidelines
Online Package Database
Security Announcements
Staffing Needs
Supporting Vendors
View our CVS

Graphics:
Logos and themes
Icons
ScreenShots

Miscellaneous Resources:
Gentoo Linux Store
Gentoo-hosted projects
IBM dW/Intel article archive




List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Mike Frysinger <vapier@g.o>
Subject: Re: RFC: multilib and the compatibility to singlelib
Date: Tue, 20 Oct 2009 14:16:01 -0400
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:
signature.asc (This is a digitally signed message part.)
Replies:
Re: RFC: multilib and the compatibility to singlelib
-- Michael Haubenwallner
References:
RFC: multilib and the compatibility to singlelib
-- Michael Haubenwallner
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: RFC: multilib and the compatibility to singlelib
Next by thread:
Re: RFC: multilib and the compatibility to singlelib
Previous by date:
Re: Support for multiple ABIs for amd64 (64bit,32bit) in multilib overlay
Next by date:
KDE Team Meeting - October 2009


Updated Nov 24, 2009

Donate to support our development efforts.

Gentoo Centric Hosting: vr.org

VR Hosted

Tek Alchemy

Tek Alchemy

SevenL.net

SevenL.net

php|architect

php|architect

Copyright 2001-2007 Gentoo Foundation, Inc. Questions, Comments? Email www@gentoo.org.