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 08:16:18 +0000 [thread overview] Message-ID: <bug-109602-4-Pak3JNH7PQ@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 ---------------------------------------------------------------------------- CC| |arsen at gcc dot gnu.org --- Comment #3 from Arsen Arsenović <arsen at gcc dot gnu.org> --- this patch is not upstream because we haven't proposed it for inclusion in the tree yet. if concerned with gentoo packaging, please open a bug on our bug tracker or talk to us on #gentoo-toolchain on libera.chat (In reply to Andrew Pinski from comment #1) > I am 99% sure this patch is not portable at all. In that not all env > supports --unset. this is part of the reason why we have not done so. (In reply to Andrew Pinski from comment #2) > Second who sets LD_LIBRARY_PATH in the first place. > Third these I thought was only done for maintenance mode. GCC tarballs appear to lack .mo files entirely (checked gcc-12.2.0.tar.xz and gcc-14-20230423.tar.xz) in all components, so this step would necessarily run. the LD_LIBRARY_PATH is set through RPATH_ENVVAR when partway through bootstrapping: LD_LIBRARY_PATH=/home/arsen/gcc/releases/gcc-11b/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs:/home/arsen/gcc/releases/gcc-11b/x86_64-pc-linux-gnu/libgomp/.libs:/home/arsen/gcc/releases/gcc-11b/x86_64-pc-linux-gnu/libitm/.libs:/home/arsen/gcc/releases/gcc-11b/./gcc:/home/arsen/gcc/releases/gcc-11b/./prev-gcc this is done, it'd seem, through all-target-libstdc++-v3 -> RAW_CXX_TARGET_EXPORTS -> BASE_TARGET_EXPORTS this happens on the 13 branch as well, but is not noticeable since that's not a downgrade on my system. it's a bit unsafe to set this variable globally like this (since it affects build-machine programs like make and msgfmt and sh too), but I'm not sure how one could avoid it, since the configure script needs it set, but not the shell that runs it, etc.. (and, even worse, only some programs configure runs need it set..) maybe it'd be easier to inject a runpath into linker flags or something? not all things can be fixed by patching like the msgfmt patch
next prev parent reply other threads:[~2023-04-24 8:16 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 [this message] 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-Pak3JNH7PQ@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: linkBe 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).