public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] RFC: masking old versions of sys-devel/gcc
Date: Wed, 26 Apr 2017 10:59:32 -0400	[thread overview]
Message-ID: <CAJ0EP40AnMG25C3gXcgjc1T8e7GpThq=XXv1QESNMuqEr5LG+Q@mail.gmail.com> (raw)
In-Reply-To: <33941528.YhSZt8Px0E@pinacolada>

On Wed, Apr 26, 2017 at 5:32 AM, Andreas K. Huettel
<dilfridge@gentoo.org> wrote:
> Am Mittwoch, 26. April 2017, 02:37:17 CEST schrieb Francesco Riosa:
>> 2017-04-26 0:26 GMT+02:00 Andreas K. Huettel <dilfridge@gentoo.org>:
>> > Am Sonntag, 23. April 2017, 14:35:48 CEST schrieb Michał Górny:
>> > > Hi,
>> > >
>> > > I'm thinking of masking old versions of sys-devel/gcc, in particular
>> > > older than the 4.9 branch.
>> >
>> > Masking is fine; some time later (maybe in a few months) I'd even suggest
>> > masking all of gcc-4. After all, unmasking them if you really need them is
>> > rather easy.
>>
>> well if the intent is cleaning adding a package mask is just more burden,
>> not less.
>> If they compile fine with the latest stable gcc better leave them unmasked,
>> right?
>
> Except that "switching back" from gcc-5 to gcc-4 doesn't really work, and that
> gcc-4 will happily use gcc-5 libraries, with unintended consequences.

What do you mean by "gcc-4 will happily use gcc-5 libraries"?

If you mean at build time, it does NOT use gcc-5 libs. If it does, that's a bug.

% gcc-4.9.4 --print-search-dirs | grep ^libraries:
libraries: =/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/:/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/../../../../x86_64-pc-linux-gnu/lib/x86_64-pc-linux-gnu/4.9.4/:/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/../../../../x86_64-pc-linux-gnu/lib/../lib64/:/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/../../../x86_64-pc-linux-gnu/4.9.4/:/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/../../../../lib64/:/lib/x86_64-pc-linux-gnu/4.9.4/:/lib/../lib64/:/usr/lib/x86_64-pc-linux-gnu/4.9.4/:/usr/lib/../lib64/:/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/../../../../x86_64-pc-linux-gnu/lib/:/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/../../../:/lib/:/usr/lib/

If you mean runtime, that's controlled by
/etc/ld.so.conf.d/05gcc-x86_64-pc-linux-gnu.conf. There's really
nothing wrong with using a newer libstdc++ at runtime; they should be
ABI compatible.


  reply	other threads:[~2017-04-26 15:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-23 12:35 [gentoo-dev] RFC: masking old versions of sys-devel/gcc Michał Górny
2017-04-24 16:01 ` William Hubbs
2017-04-24 17:59   ` Guilherme Amadio
2017-04-25 16:26     ` William Hubbs
2017-04-25 16:44       ` Guilherme Amadio
2017-04-25 18:38         ` Francesco Riosa
2017-04-25 22:26 ` Andreas K. Huettel
2017-04-26  0:37   ` Francesco Riosa
2017-04-26  9:32     ` Andreas K. Huettel
2017-04-26 14:59       ` Mike Gilbert [this message]
2017-04-27  2:08       ` Walter Dnes
2017-04-27 15:27   ` William Hubbs
2017-04-27 22:56     ` Andrew Savchenko
2017-04-26  9:42 ` Chí-Thanh Christopher Nguyễn
2017-04-26 12:22   ` Michał Górny

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='CAJ0EP40AnMG25C3gXcgjc1T8e7GpThq=XXv1QESNMuqEr5LG+Q@mail.gmail.com' \
    --to=floppym@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