public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mkrupcale at matthewkrupcale dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++ Date: Sat, 24 Jul 2021 23:18:38 +0000 [thread overview] Message-ID: <bug-87858-4-451jJpzIBq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-87858-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858 --- Comment #8 from Matthew Krupcale <mkrupcale at matthewkrupcale dot com> --- (In reply to Andrew Pinski from comment #7) > You misunderstood. Building a cross compiler and a canadian cross is so the > new 4.8 compiler is NOT exposing to the bootstrap issue you mentioned. Fair enough, that seems likely to work as well. But you still need to build that initial compiler with the newer compiler. > 4.8 and 8.x are no longer maintained so fixing those are out of the question. I'm not suggesting to patch 4.8 or 8.x series. I'm suggesting that the issue still likely exists on the latest GCC. Of course you won't be able to verify that unless you intentionally create some new ABI in libstdc++ which is also used by the host programs and then try to build the old ABI libstdc++ with the the new one on the build host. That's why it took so long to verify that GCC 8 had the issue (as well as all versions between 4.8 and 8) and is likely still in the latest version. > stage1 of gcc does not require the LD_LIBRARY_PATH to be set at all I may be using the wrong name--perhaps it's not LD_LIBRARY_PATH specifically, but the effect is similar. My patch actually modifies the RPATH_ENVVAR to not include the target libstdc++ path during stage1 of the bootstrap since the stage1 host binaries depend on the build host libstdc++. Then in stages 2 and 3 the RPATH_ENVVAR can include the target libstdc++ path and build successfully.
next prev parent reply other threads:[~2021-07-24 23:18 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-87858-4@http.gcc.gnu.org/bugzilla/> 2020-12-21 18:36 ` mkrupcale at matthewkrupcale dot com 2021-04-01 13:48 ` libor.bukata at oracle dot com 2021-07-24 20:31 ` pinskia at gcc dot gnu.org 2021-07-24 22:07 ` mkrupcale at matthewkrupcale dot com 2021-07-24 22:23 ` pinskia at gcc dot gnu.org 2021-07-24 23:18 ` mkrupcale at matthewkrupcale dot com [this message] 2022-06-18 23:13 ` edgargar at unam dot mx 2023-05-29 17:59 ` mkrupcale at matthewkrupcale dot com 2023-05-29 18:00 ` mkrupcale at matthewkrupcale dot com 2023-05-29 18:10 ` mkrupcale at matthewkrupcale dot com 2023-12-30 11:57 ` xry111 at gcc dot gnu.org 2023-12-30 12:02 ` xry111 at gcc dot gnu.org 2023-12-30 19:32 ` eyalroz1 at gmx dot com
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-87858-4-451jJpzIBq@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).