public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/105688] Cannot build GCC 11.3 on Fedora 36 Date: Mon, 23 May 2022 15:27:52 +0000 [thread overview] Message-ID: <bug-105688-4-TVRkR0xxIF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105688-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688 Alexander Monakov <amonakov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amonakov at gcc dot gnu.org --- Comment #12 from Alexander Monakov <amonakov at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #7) > /usr/bin/ld: > /tmp/OBJDIR/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.so.6: > version `GLIBCXX_3.4.30' not found (required by /usr/bin/ld) > > > The problem is not realted to GCC directly but rather ld being linked > against a newer version of libstdc++ and now you just compiled an older > version of libstdc++ and that is in the LD_LIBRARY_PATH some how ... Which > should not happen .... Could libtool be erroneously populating LD_LIBRARY_PATH? > If anything this should be reported to binutils and have ld (I suspect gold > here) use -static-libstdc++ -static-libgcc while linking just the same way > GCC does. No, this doesn't make sense, ld shouldn't work around wrong LD_LIBRARY_PATH setting.
next prev parent reply other threads:[~2022-05-23 15:27 UTC|newest] Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-22 10:02 [Bug c/105688] New: " aros at gmx dot com 2022-05-22 10:52 ` [Bug c/105688] " aros at gmx dot com 2022-05-22 11:04 ` aros at gmx dot com 2022-05-22 12:57 ` pinskia at gcc dot gnu.org 2022-05-22 12:59 ` aros at gmx dot com 2022-05-22 13:00 ` aros at gmx dot com 2022-05-23 7:24 ` rguenth at gcc dot gnu.org 2022-05-23 7:31 ` pinskia at gcc dot gnu.org 2022-05-23 7:32 ` [Bug bootstrap/105688] " pinskia at gcc dot gnu.org 2022-05-23 7:35 ` pinskia at gcc dot gnu.org 2022-05-23 7:37 ` aros at gmx dot com 2022-05-23 14:13 ` aros at gmx dot com 2022-05-23 15:27 ` amonakov at gcc dot gnu.org [this message] 2022-05-23 18:36 ` pinskia at gcc dot gnu.org 2022-05-23 23:35 ` aros at gmx dot com 2022-05-23 23:48 ` pinskia at gcc dot gnu.org 2022-05-23 23:51 ` pinskia at gcc dot gnu.org 2022-05-23 23:52 ` sam at gentoo dot org 2022-05-24 9:07 ` aros at gmx dot com 2022-05-24 9:10 ` aros at gmx dot com 2022-05-24 9:11 ` pinskia at gcc dot gnu.org 2022-07-04 15:02 ` vincent-gcc at vinc17 dot net 2022-07-04 16:20 ` redi at gcc dot gnu.org 2022-07-04 16:23 ` redi at gcc dot gnu.org 2022-07-04 16:24 ` sam at gentoo dot org 2022-07-04 16:26 ` aros at gmx dot com 2022-07-05 8:53 ` vincent-gcc at vinc17 dot net 2022-07-05 16:08 ` redi at gcc dot gnu.org 2022-07-05 17:40 ` aros at gmx dot com 2022-07-05 18:04 ` [Bug bootstrap/105688] GCC 11.3 doesn't build with the GNU gold linker (version 2.37-27.fc36) 1.16: libstdc++.so.6: version `GLIBCXX_3.4.30' not found aros at gmx dot com 2022-07-05 18:27 ` aros at gmx dot com 2022-07-05 18:30 ` aros at gmx dot com 2022-07-06 1:48 ` pinskia at gcc dot gnu.org 2022-07-06 2:48 ` vincent-gcc at vinc17 dot net 2022-07-06 2:54 ` pinskia at gcc dot gnu.org 2022-07-06 2:59 ` vincent-gcc at vinc17 dot net 2022-07-06 3:06 ` vincent-gcc at vinc17 dot net 2022-07-06 3:14 ` pinskia at gcc dot gnu.org 2022-07-06 7:08 ` redi at gcc dot gnu.org 2022-07-06 9:43 ` vincent-gcc at vinc17 dot net 2022-07-06 10:52 ` aros at gmx dot com 2022-07-06 12:17 ` redi at gcc dot gnu.org 2022-07-06 15:29 ` aros at gmx dot com 2022-07-20 15:12 ` redi at gcc dot gnu.org 2023-04-24 19:46 ` arsen at gcc dot gnu.org 2023-04-24 19:55 ` arsen at gcc dot gnu.org 2024-01-24 10:28 ` [Bug bootstrap/105688] GCC breaks build process if bootstrapping a downgraded GCC (was "GCC 11.3 doesn't build with the GNU gold linker (version 2.37-27.fc36) 1.16: libstdc++.so.6: version `GLIBCXX_3.4.30' not found") redi at gcc dot gnu.org 2024-01-24 19:14 ` jason at gcc dot gnu.org 2024-01-24 22:37 ` jason 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-105688-4-TVRkR0xxIF@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).