public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vincent Lefevre <vincent+gcc@vinc17.org>
To: 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 14:54:06 +0200	[thread overview]
Message-ID: <20220704125406.GC1130636@zira.vinc17.org> (raw)
In-Reply-To: <CAH6eHdQ5eDLS793j2yTquweoSJpUeYnZL5S5sfGmXqQav6x+Ag@mail.gmail.com>

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)

With a54ce8865a885bca5ab9c4aa6ec725cd13c09901, this is:

/usr/bin/msgfmt: symbol lookup error: /usr/lib/x86_64-linux-gnu/libicuuc.so.71: undefined symbol: _ZNSt18condition_variable4waitERSt11unique_lockISt5mutexE, version GLIBCXX_3.4.30

> Something is setting LD_LIBRARY_PATH so that the newly-built
> libstdc++.so is being used.

Indeed, using a wrapper with "printenv LD_LIBRARY_PATH" for msgfmt,
I get:

LD_LIBRARY_PATH: /home/vlefevre/software/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs:/home/vlefevre/software/gcc-build/x86_64-pc-linux-gnu/libsanitizer/.libs:/home/vlefevre/software/gcc-build/x86_64-pc-linux-gnu/libvtv/.libs:/home/vlefevre/software/gcc-build/x86_64-pc-linux-gnu/libssp/.libs:/home/vlefevre/software/gcc-build/x86_64-pc-linux-gnu/libgomp/.libs:/home/vlefevre/software/gcc-build/x86_64-pc-linux-gnu/libitm/.libs:/home/vlefevre/software/gcc-build/x86_64-pc-linux-gnu/libatomic/.libs:/home/vlefevre/software/gcc-build/./gcc:/home/vlefevre/software/gcc-build/./prev-gcc

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

  parent reply	other threads:[~2022-07-04 12:54 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
2022-07-04 12:54   ` Vincent Lefevre [this message]
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=20220704125406.GC1130636@zira.vinc17.org \
    --to=vincent+gcc@vinc17.org \
    --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).