public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <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 22:23:00 +0000 [thread overview]
Message-ID: <bug-87858-4-JgKqIQuX4y@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
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WONTFIX |---
Status|RESOLVED |UNCONFIRMED
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Matthew Krupcale from comment #6)
> (In reply to Andrew Pinski from comment #5)
> > Best way to support this really is to build a 4.8 cross compiler and then
> > build a canandian cross GCC 4.8 and then bootstrap a 4.8.x using that newly
> > build canandian cross compiler.
>
> I'm not sure I follow exactly because I wasn't trying to build a cross
> compiler, although I suppose once you have a GCC 4.8 compiler built (cross
> or not), you wouldn't have a problem building 4.8.x with it in theory. But
> the problem is building that initial GCC 4.8 (cross or not) with the newer
> GCC version.
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.
4.8 and 8.x are no longer maintained so fixing those are out of the question.
stage1 of gcc does not require the LD_LIBRARY_PATH to be set at all and stage 2
and 3 will use -static-libstdc++.
Of course LD_LIBRARY_PATH shouldn't be needed these days.
next prev parent reply other threads:[~2021-07-24 22:23 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 [this message]
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
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-JgKqIQuX4y@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).