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: Mon, 29 May 2023 18:10:00 +0000	[thread overview]
Message-ID: <bug-87858-4-hFTiH8ucb6@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 #12 from Matthew Krupcale <mkrupcale at matthewkrupcale dot com> ---
I've updated the patch to include the target libstdc++ path on LD_LIBRARY_PATH
only after stage1 for both host and target module exports--that is, previously,
the patches only modified the LD_LIBRARY_PATH exports for target modules,
whereas the new version does the same for host modules as well. This fixes an
issue I found while building GCC 7 on RHEL 9 in which the gotools host module
failed to build with similar ABI issues as described in this thread.

See my copr repos [1,2] for both GCC 7 and 8 now both building with the
respective patches on multiple OS (RHEL 9, Fedora 37, 38), architectures
(aarch64, ppc64le, s390x, x86_64), and host GCC versions (11.3, 12.2, 13.0).

(In reply to Libor Bukata from comment #4)
> We also cannot build older GCC versions with GCC 11 nightly (commit
> 8a6a62614a8ae) on Solaris Trunk:
> ...
> 
> GLIBCXX_3.4.29 is a new addition to libstdc++.so.6 that is not available in
> older libstdc++.so.6 libraries of GCC 7, 9, and 10.

Without the patches, I did also observe the issue Libor Bukata saw in comment
#4 while building GCC 7 or 8 with GCC 11.

(In reply to Ed Gar from comment #9)
> I confirm that the issue persists even when using either patch suggested by
> Matthew Krupcale.

I was unable to reproduce your build issue with my patches.

[1] https://copr.fedorainfracloud.org/coprs/mkrupcale/gcc-7/build/5787271/
[2] https://copr.fedorainfracloud.org/coprs/mkrupcale/gcc-8/build/5798225/

  parent reply	other threads:[~2023-05-29 18:10 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
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 [this message]
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-hFTiH8ucb6@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).