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] {bi,multi}arch support for all x86/amd64/ppc/sparc systems
Date: Fri, 27 Jan 2012 16:00:15 -0500	[thread overview]
Message-ID: <201201271600.15986.vapier@gentoo.org> (raw)
In-Reply-To: <201112071715.48319.vapier@gentoo.org>

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

On Wednesday 07 December 2011 17:15:47 Mike Frysinger wrote:
> the advantage is that it should obsolete the separate kgcc64 package for
> most people.  and i think it might help out with the multilib bootstrap
> issue: you can't build multilib gcc without a multilib glibc, and can't
> build a multilib glibc without a multilib gcc, but i think you should be
> able to build a multilib glibc with a multiarch gcc, and then a multilib
> gcc after that.

a followup: have glibc always install headers for all possible ABIs.  this 
might sound like a lot, but in practice, it amounts to only a handful as glibc 
by default includes support for all ABIs in common headers.

the most common example:
 - amd64 ABI has one unshared header: gnu/stubs-64.h
 - x86 ABI has three unshared headers: gnu/stubs-32.h sys/elf.h sys/vm86.h

so the overhead we're talking about here is that nomultilib amd64 systems will 
have 3 additional headers installed, and nomultilib x86 systems will have one 
extra header.  i suspect the overhead will be very similar for all arches.

the reason for doing this is to try and make multilib migration simpler.  with 
this change in place, you should be able to "upgrade" from a nomultilib amd64 
profile to a multilib amd64 profile with:
	USE='-*' emerge sys-devel/gcc
	emerge sys-libs/glibc
	emerge sys-devel/gcc

still not as automatic as i'd like, but getting closer ...
-mike

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

      parent reply	other threads:[~2012-01-27 21:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 22:15 [gentoo-dev] {bi,multi}arch support for all x86/amd64/ppc/sparc systems Mike Frysinger
2011-12-07 23:41 ` Mike Frysinger
2011-12-08  2:12 ` [gentoo-dev] " Duncan
2011-12-08  2:40   ` Ryan Hill
2011-12-08  3:34   ` Mike Frysinger
2011-12-11 21:01 ` [gentoo-dev] " Mike Frysinger
2012-01-27 21:00 ` Mike Frysinger [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=201201271600.15986.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