From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 0725F3856DD8; Mon,  4 Jul 2022 15:02:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0725F3856DD8
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/105688] Cannot build GCC 11.3 on Fedora 36
Date: Mon, 04 Jul 2022 15:02:39 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 11.3.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vincent-gcc at vinc17 dot net
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-105688-4-12MbbEfTOq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-105688-4@http.gcc.gnu.org/bugzilla/>
References: <bug-105688-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2022 15:02:40 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D105688

--- Comment #21 from Vincent Lef=C3=A8vre <vincent-gcc at vinc17 dot net> -=
--
I have a similar issue under Debian/unstable with GCC old of a few months,
where in x86_64-pc-linux-gnu/libstdc++-v3/po, msgfmt fails with an error li=
ke

/usr/bin/msgfmt:
/home/vlefevre/software/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/src/.lib=
s/libstdc++.so.6:
version `GLIBCXX_3.4.30' not found (required by
/usr/lib/x86_64-linux-gnu/libicuuc.so.71)

A msgfmt wrapper with "printenv LD_LIBRARY_PATH" shows that LD_LIBRARY_PATH=
 is
set to

/home/vlefevre/software/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/src/.lib=
s:/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/vl=
efevre/software/gcc-build/x86_64-pc-linux-gnu/libssp/.libs:/home/vlefevre/s=
oftware/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-bui=
ld/x86_64-pc-linux-gnu/libatomic/.libs:/home/vlefevre/software/gcc-build/./=
gcc:/home/vlefevre/software/gcc-build/./prev-gcc

This bug is probably still present in master: I do not get any failure,
probably because the built libstdc++.so.6 is recent enough to be similar to=
 the
one currently provided by Debian/unstable, but the wrapper still shows that
LD_LIBRARY_PATH is set to the above string (or similar), so that the bug co=
uld
still occur when the system libstdc++.so.6 gets something new.

I suppose that LD_LIBRARY_PATH is set because it is needed in order to use
built libraries. But perhaps that instead, a run path should be used togeth=
er
with --disable-new-dtags (so that it overrides the user's LD_LIBRARY_PATH).=