From: Sergei Trofimovich <slyfox@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New USE=-native-symlinks for gcc-config and binutils-config
Date: Sun, 24 May 2020 10:34:56 +0100 [thread overview]
Message-ID: <20200524103456.0c0caad0@sf> (raw)
In-Reply-To: <CAEdQ38F5SdcHdLyrmXGbt3Th4k8Nz=B=05iudt5qcLEdQmpt6w@mail.gmail.com>
On Sat, 23 May 2020 23:40:22 -0700
Matt Turner <mattst88@gentoo.org> wrote:
> On Sat, May 23, 2020 at 10:21 PM Joonas Niilola <juippis@gentoo.org> wrote:
> >
> >
> > On 5/24/20 5:41 AM, Mike Gilbert wrote:
> > > Also, people are likely to disable this accidentally via USE="-*".
> >
> > Counts as
> >
> > > if they want to break their system intentionally.
>
> Yes, but unfortunately catalyst's stage1 build does exactly this.
>
> Suggestions how to avoid doing this would be appreciated, but until
> that's resolved we don't have carte blanche to break USE="-*".
Ah, I keep forgetting about catalyst. Use-forced flags as:
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0f8b5b847429642977d4c0497068a93222ff3136
While at it added a page that explains how to turn it back by enthusiasts:
https://wiki.gentoo.org/wiki/Project:Toolchain/use_native_symlinks
and will collect more details on typical fixes and "this is fine to ignore" pitfalls.
--
Sergei
next prev parent reply other threads:[~2020-05-24 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 21:36 [gentoo-dev] New USE=-native-symlinks for gcc-config and binutils-config Sergei Trofimovich
2020-05-23 6:05 ` Michał Górny
2020-05-23 7:24 ` Sergei Trofimovich
2020-05-24 1:40 ` Pengcheng Xu
2020-05-24 7:55 ` Kent Fredric
2020-05-24 10:04 ` Sergei Trofimovich
2020-05-24 2:41 ` Mike Gilbert
2020-05-24 5:20 ` Joonas Niilola
2020-05-24 6:40 ` Matt Turner
2020-05-24 9:34 ` Sergei Trofimovich [this message]
2020-05-24 8:15 ` Kent Fredric
2020-05-24 8:33 ` Michał Górny
2020-05-24 9:15 ` Kent Fredric
2020-05-24 9:48 ` Sergei Trofimovich
2020-05-24 10:00 ` Fabian Groffen
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=20200524103456.0c0caad0@sf \
--to=slyfox@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