From: Xi Ruoyao <xry111@xry111.site>
To: "Salvatore Filippone" <filippone.salvatore@gmail.com>,
"Arsen Arsenovi�0�4" <arsen@aarsen.me>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Bootstrap failure on Fedora 37
Date: Wed, 22 Feb 2023 01:02:06 +0800 [thread overview]
Message-ID: <732016f750d521816906d6c0deef3df7a782cc90.camel@xry111.site> (raw)
In-Reply-To: <CANSzZf5sMk7zjUbBDTyMGOYJiXfqV1fmR=n+rDDdtpBsr8TGMw@mail.gmail.com>
On Tue, 2023-02-21 at 17:56 +0100, Salvatore Filippone via Gcc-help
wrote:
> --disable-libsanitizer works for me on GCC 11.3.0, thanks.
>
> Now, on bootstrapping 10.4.0 I get a different error. Suggestions?
> Thanks
Install the static library libstdc++.a via the package manager of your
distro.
GCC building system normally links the newly built GCC to libstdc++.a.
But if there is no libstdc++.a available, it will link to libstdc++.so.
The bootstrapping process will then create another libstdc++.so and
attempt to use it, which in your case is less capable than the system
one and causing a failure like this.
>
> -------------------------------------------------
> /data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/./gcc/xgcc -shared-libgcc
> -B/data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/./gcc -nostdinc++
> -L/data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/x86_64-pc-linux-
> gnu/32/libstdc++-v3/src
> -L/data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/x86_64-pc-linux-
> gnu/32/libstdc++-v3/src/.libs
> -L/data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/x86_64-pc-linux-
> gnu/32/libstdc++-v3/libsupc++/.libs
> -B/opt/gnu/10.4.0/x86_64-pc-linux-gnu/bin/
> -B/opt/gnu/10.4.0/x86_64-pc-linux-gnu/lib/ -isystem
> /opt/gnu/10.4.0/x86_64-pc-linux-gnu/include -isystem
> /opt/gnu/10.4.0/x86_64-pc-linux-gnu/sys-include -fno-checking -m32 -x
> c++-header -nostdinc++ -g -O2 -D_GNU_SOURCE -m32
> -I/data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/x86_64-pc-linux-
> gnu/32/libstdc++-v3/include/x86_64-pc-linux-gnu
> -I/data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/x86_64-pc-linux-
> gnu/32/libstdc++-v3/include
> -I/data/travel/SOFTWARE/GNU/BUILDS/gcc-10.4.0/libstdc++-v3/libsupc++
> -O2
> -g
> /data/travel/SOFTWARE/GNU/BUILDS/gcc-10.4.0/libstdc++-
> v3/include/precompiled/stdc++.h
> -o x86_64-pc-linux-gnu/bits/stdc++.h.gch/O2g.gch
> /data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/./gcc/cc1plus:
> /data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/x86_64-pc-linux-
> gnu/libstdc++-v3/src/.libs/libstdc++.so.6:
> version `GLIBCXX_3.4.29' not found (required by
> /data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/./gcc/cc1plus)
> /data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/./gcc/cc1plus:
> /data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/x86_64-pc-linux-
> gnu/libstdc++-v3/src/.libs/libstdc++.so.6:
> version `GLIBCXX_3.4.29' not found (required by
> /data/travel/SOFTWARE/GNU/BUILDS/obj-10.4.0/./gcc/cc1plus)
> make[9]: *** [Makefile:1826:
> x86_64-pc-linux-gnu/bits/stdc++.h.gch/O2ggnu++0x.gch] Errore 1
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-02-21 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 15:48 Salvatore Filippone
2023-02-21 15:58 ` Arsen Arsenović
2023-02-21 16:56 ` Salvatore Filippone
2023-02-21 17:02 ` Xi Ruoyao [this message]
2023-02-22 8:11 ` Salvatore Filippone
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=732016f750d521816906d6c0deef3df7a782cc90.camel@xry111.site \
--to=xry111@xry111.site \
--cc=arsen@aarsen.me \
--cc=filippone.salvatore@gmail.com \
--cc=gcc-help@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).