build failure of old GCC: .../libstdc++.so.6: version `GLIBCXX_3.4.30' not found

Jonathan Wakely jwakely.gcc@gmail.com
Mon Jul 4 12:50:14 GMT 2022


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.


More information about the Gcc-help mailing list