public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: {bi,multi}arch support for all x86/amd64/ppc/sparc systems
Date: Thu, 8 Dec 2011 02:12:37 +0000 (UTC)	[thread overview]
Message-ID: <pan.2011.12.08.02.12.37@cox.net> (raw)
In-Reply-To: 201112071715.48319.vapier@gentoo.org

Mike Frysinger posted on Wed, 07 Dec 2011 17:15:47 -0500 as excerpted:

> 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.

1) Will this allow building grub from amd64/no-multilib, thus avoiding 
having to have grub-static?  That's the one thing I don't like about no-
multilib, having to use the pre-built grub-static.

2) What about grub-2, and while we're on it, is a switch to that expected 
any time soon, and/or is there a grub-static-2 in the wings?  With the 
grub-1 gpt patches (and hopefully btrfs support at some point) I'm not 
sure that staying with grub-1 isn't my preference in any case, but I do 
worry how long that's going to be viable, especially with btrfs coming 
and no grub-1 btrfs support that I'm aware of, and I have literally /no/ 
idea what might or might not be in gentoo's pipeline,
grub-wise.

3) One thing I very much like about no-multilib is the shorter gcc (and 
glibc) builds.  This will kill that (for gcc), right?  USE flag activated 
to avoid that for those who want to?  (Of course I realize that it's 
unlikely I can keep/get both the shorter gcc builds and support for grub 
builds.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  parent reply	other threads:[~2011-12-08  2:13 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 ` Duncan [this message]
2011-12-08  2:40   ` [gentoo-dev] " 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

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=pan.2011.12.08.02.12.37@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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