From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: build failure of old GCC: .../libstdc++.so.6: version `GLIBCXX_3.4.30' not found
Date: Mon, 4 Jul 2022 13:50:14 +0100 [thread overview]
Message-ID: <CAH6eHdRt0E0K_PKi51-GJE61+ZCtk=4i7=iKiSCQCFEUkBPy=Q@mail.gmail.com> (raw)
In-Reply-To: <20220704123331.GB1130636@zira.vinc17.org>
On Mon, 4 Jul 2022 at 13:34, Vincent Lefevre <vincent+gcc@vinc17.org> wrote:
>
> On 2022-07-04 13:13:58 +0100, Jonathan Wakely via Gcc-help wrote:
> > On Mon, 4 Jul 2022 at 12:58, Vincent Lefevre <vincent+gcc@vinc17.org> wrote:
> > >
> > > On a Debian/unstable machine, I'm trying to build old GCC, such as
> > > one based on 0cc79337ad265aabccab63882a810f9dc509a9d0 (2021-04-20).
> > > I'm using
> > >
> > > ../gcc-trunk/configure --prefix=$HOME/opt/gcc-trunk \
> > > --enable-multiarch \
> > > --enable-languages=c \
> > > --program-suffix=-test
> > >
> > > but "make" gives the following error:
> > >
> > > /usr/bin/msgfmt: /home/vlefevre/software/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /usr/lib/x86_64-linux-gnu/libicuuc.so.71)
> >
> > Something is setting LD_LIBRARY_PATH so that the newly-built
> > libstdc++.so is being used.
>
> Is the the same bug (or a similar one) as this one?
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688
Yes, it could be.
>
> (though the error doesn't occur at the same place).
>
> > Where in the build does it fail? I don't think LD_LIBRARY_PATH should
> > be set until running the testsuites.
>
> [...]
> make[5]: Entering directory '/home/vlefevre/software/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/po'
> msgfmt -o de.mo ../../../../gcc-trunk/libstdc++-v3/po/de.po
> [...]
>
> If I run "make" from this directory, I don't get any error.
next prev parent reply other threads:[~2022-07-04 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 11:57 Vincent Lefevre
2022-07-04 12:13 ` Jonathan Wakely
2022-07-04 12:33 ` Vincent Lefevre
2022-07-04 12:50 ` Jonathan Wakely [this message]
2022-07-04 12:54 ` Vincent Lefevre
2022-07-18 16:34 ` Jonathan Wakely
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='CAH6eHdRt0E0K_PKi51-GJE61+ZCtk=4i7=iKiSCQCFEUkBPy=Q@mail.gmail.com' \
--to=jwakely.gcc@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).