public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arsen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109602] Import Gentoo msgfmt patch ?
Date: Mon, 24 Apr 2023 19:46:12 +0000 [thread overview]
Message-ID: <bug-109602-4-dA8ht7Y1X4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109602-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109602
Arsen Arsenović <arsen at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Arsen Arsenović <arsen at gcc dot gnu.org> ---
(In reply to Romain Geissler from comment #5)
> Hi,
>
> My intention was to try to raise upstream an issue that people packaging gcc
> may hit in some cases. Gentoo has such a patch, but I also have a similar
> one on my side since couple of years, it's only yesterday that I discovered
> Gentoo had one too (and Alpine Linux). I am not a user of Gentoo nor Alpine
> Linux myself, I just also package my own gcc.
>
> So I apologize to the Gentoo and Gcc communities if I offended anyone by
> opening this bug report, that was not the intention.
no worries, I doubt anyone took offense. we (Gentoo) try to work as closely as
possible with upstream GCC, so usually a patch being on our end only means that
nobody reworked it to be upstreamable. if in doubt, you can email
toolchain@gentoo.org - we'd be happy to answer.
in this instance, the 'fix' we use is not applicable in the general case, since
it doesn't solve the general problem of building a downgraded gcc, so we never
upstreamed it.
PS: the general issue is reported, marking as dupe
have a lovely day!
*** This bug has been marked as a duplicate of bug 105688 ***
prev parent reply other threads:[~2023-04-24 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 0:09 [Bug libstdc++/109602] New: " romain.geissler at amadeus dot com
2023-04-24 0:12 ` [Bug libstdc++/109602] " pinskia at gcc dot gnu.org
2023-04-24 0:14 ` pinskia at gcc dot gnu.org
2023-04-24 8:16 ` arsen at gcc dot gnu.org
2023-04-24 12:37 ` sjames at gcc dot gnu.org
2023-04-24 12:42 ` romain.geissler at amadeus dot com
2023-04-24 19:46 ` arsen at gcc dot gnu.org [this message]
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=bug-109602-4-dA8ht7Y1X4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).