public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: About gcc-4.6 unmasking
Date: Tue, 21 Feb 2012 10:26:38 +0100	[thread overview]
Message-ID: <1329816398.2868.1.camel@belkin4> (raw)
In-Reply-To: <20120220200220.3a54d88a@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]

El lun, 20-02-2012 a las 20:02 -0600, Ryan Hill escribió:
> On Mon, 20 Feb 2012 17:17:30 -0800
> Zac Medico <zmedico@gentoo.org> wrote:
> 
> > On 02/20/2012 05:03 PM, Ryan Hill wrote:
> > > On Mon, 20 Feb 2012 21:34:14 +0100
> > > Pacho Ramos <pacho@gentoo.org> wrote:
> > > 
> > >> I don't know if this has been discussed before but, what issues are
> > >> preventing us from unmasking gcc-4.6 (and think on a near
> > >> stabilization)?
> > >>
> > >> I have read hardmask message but it simply explains that it's masked for
> > >> testing purposes :-/
> > > 
> > > Grub is the only blocker.  I don't want to unmask something that makes
> > > people's systems unbootable.
> > > 
> > > I'm also out of ideas and open to suggestions.
> > 
> > Stabilize grub-1.99, and modify the grub-0.9x ebuilds to die if they
> > can't find a supported compiler.
> 
> What's the state of 1.99?  I know someone was working on it recently.  We'd
> also have to update the handbooks.  I think it could be several months of
> work to get it ready, and I'd like to unmask 4.6 last September.
> 
> 

As looks like fixing old grub is far away because nobody know what is
causing that issues, probably trying to get grub-1.99 ready for
stabilization would be interesting (we will need to do that sooner or
later anyway)

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

  reply	other threads:[~2012-02-21  9:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 20:34 [gentoo-dev] About gcc-4.6 unmasking Pacho Ramos
2012-02-20 20:41 ` Justin
2012-02-20 20:49   ` Pacho Ramos
2012-02-20 23:47     ` Andreas K. Huettel
     [not found]   ` <b3e3c3fc72414f81893a33973065c059@HUBCAS2.cs.stonybrook.edu>
2012-02-20 21:26     ` Richard Yao
2012-02-21  1:03 ` [gentoo-dev] " Ryan Hill
2012-02-21  1:16   ` Matt Turner
2012-02-21  1:17   ` Zac Medico
2012-02-21  2:02     ` Ryan Hill
2012-02-21  9:26       ` Pacho Ramos [this message]
2012-02-21 22:38         ` Alec Warner
2012-02-21 22:50           ` Mike Gilbert
2012-02-21 22:57           ` Nikos Chantziaras
2012-02-22  4:22             ` Ben
2012-02-22  5:36               ` Alec Warner
2012-02-22  5:39                 ` Robin H. Johnson
2012-02-22  8:54               ` James Cloos
2012-02-22 10:26                 ` [gentoo-dev] default to syslinux instead of grub, was " Chí-Thanh Christopher Nguyễn
2012-02-22  8:46           ` [gentoo-dev] " Duncan
2012-02-22  1:14         ` Ryan Hill
2012-02-21  1:30   ` Alexandre Rostovtsev
2012-02-21  2:00     ` Ryan Hill
2012-02-21  8:26       ` Xavier Miller
2012-02-22 10:34   ` Chí-Thanh Christopher Nguyễn
2012-02-25  3:02   ` Ryan Hill
     [not found] ` <bd23e49207bb4f44b379679256fdb19d@HUBCAS2.cs.stonybrook.edu>
2012-02-21  1:37   ` Richard Yao
2012-02-21  1:48     ` Richard Yao
2012-02-21  2:19     ` Ryan Hill

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=1329816398.2868.1.camel@belkin4 \
    --to=pacho@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