public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: gcc-6.x status inquiry
Date: Wed, 3 May 2017 14:00:26 -0400	[thread overview]
Message-ID: <71687537-4bd1-4489-9d80-246d8e2c1472@gentoo.org> (raw)
In-Reply-To: <1187ac04-2b02-6c21-e7a0-d46cf846e2a3@gentoo.org>

On 03/05/17 01:58 PM, Luca Barbato wrote:
> On 5/3/17 6:43 PM, William Hubbs wrote:
>> Hey all,
>>
>> I am asking about this because I have been asked to look into
>> packaging software that has a specific requirement for >=gcc-6 in order
>> to build [1].
> 
> As I said few times, we should dump gcc-5 sooner than later and any
> software that does not build with gcc-6 should be p.masked and dropped
> from the tree if there isn't a nice fix for it.

Just a heads-up, that p.mask list would happen to include firefox and 
thunderbird right now.


  reply	other threads:[~2017-05-03 18:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 16:43 [gentoo-dev] gcc-6.x status inquiry William Hubbs
2017-05-03 17:10 ` Hanno Böck
2017-05-03 17:58 ` [gentoo-dev] " Luca Barbato
2017-05-03 18:00   ` Ian Stakenvicius [this message]
2017-05-03 18:42     ` William Hubbs
2017-05-03 19:06       ` Ian Stakenvicius
2017-05-03 18:44     ` Erik Närström
2017-05-04  7:28     ` grozin
2017-05-04  7:48       ` Erik Närström
2017-05-03 18:57 ` [gentoo-dev] " Andreas K. Huettel
2017-05-03 19:25   ` Matthias Maier
2017-05-04 15:22     ` Thomas Deutschmann
2017-05-04 21:32       ` Getting gcc-6 keyworded (was: Re: [gentoo-dev] gcc-6.x status inquiry) Andreas K. Huettel
2017-05-04 21:33         ` Andreas K. Huettel
2017-05-04 21:20 ` [gentoo-dev] gcc-6.x status inquiry William Hubbs
2017-05-04 21:30   ` Matthias Maier

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=71687537-4bd1-4489-9d80-246d8e2c1472@gentoo.org \
    --to=axs@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