public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109602] New: Import Gentoo msgfmt patch ?
Date: Mon, 24 Apr 2023 00:09:06 +0000	[thread overview]
Message-ID: <bug-109602-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109602

            Bug ID: 109602
           Summary: Import Gentoo msgfmt patch ?
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: romain.geissler at amadeus dot com
  Target Milestone: ---

Hi,

I am wondering, would it make sense to import Gentoo's msgfmt patch ? In some
occasion, it seems that the build system of gcc/libstdc++ wrongly sets
LD_LIBRARY_PATH when building (in case it helps, in my case it seems to happens
only when doing a gcc bootstrap). I am speaking about this patch:
https://gitweb.gentoo.org/proj/gcc-patches.git/tree/10.3.0/gentoo/36_all_msgfmt-libstdc++-link.patch?id=6fb906ef2da01327d64cea263887ef34c97c1bbf
and more globally about this set of Gentoo bugs https://bugs.gentoo.org/372377
or https://bugs.gentoo.org/843119

It seems at least Alpine Linux also carries this patch:
https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/main/gcc/0009-Ensure-that-msgfmt-doesn-t-encounter-problems-during.patch

I understand the underlying issue is more that LD_LIBRARY_PATH shouldn't be
set, but it seems past investigations didn't really lead to finding this root
cause (see bug #105688), so in the meantime, maybe this workaround patch should
be imported in upstream tree directly. It's just a proposal, I would understand
this is refused.

Cheers,
Romain

             reply	other threads:[~2023-04-24  0:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24  0:09 romain.geissler at amadeus dot com [this message]
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

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@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).