From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 235633858C56; Wed, 28 Sep 2022 10:59:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 235633858C56 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1664362763; bh=W3xj/zkXwZ9ZOP5JTWYptZWXQ6LVzMtWu504vdnGv74=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SjdJHSwi4MfFUhWIWz5Aav3wvjgZootq+uXwKuYKWQOjuBD5UAUb5J+WVN3K3bCzE GG2RR4P1c4DjaSARm4zS23k2jVXItM3BiIOudLxWPcaY9OGfTORYodZIsZgiWTcf7M eWQNOeHxt7v6JbAZzpKRvv1Pxvd2fLYXlD91B7cw= From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/107059] [13 regression] bootstrap failure after r13-2887-gb04208895fed34 Date: Wed, 28 Sep 2022 10:59:22 +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: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: NEW 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: In-Reply-To: References: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107059 --- Comment #15 from Tobias Burnus --- (In reply to Jakub Jelinek from comment #13) > I wonder how it works for Tobias then. Bootstrap * works on x86_64 with Ubuntu 20.04.5 LTS (focal) with glibc 2.31-0ubuntu9= .9 * fails on ppc64le with Ubuntu 18.04.3 LTS (bionic) with glibc 2.27-3ubunt= u1 I have now done some debugging. The reason it works on x86-64 is that I have there in the $BUILD directory: gcc/include-fixed/bits -> x86_64-linux-gnu/bits That matches: /usr/include/bits -> x86_64-linux-gnu/bits=20 dpkg -S find * the symbolic link in package libc6-dev-i386 * the real 'bits' directory in package libc6-dev:amd64 On PowerPC, I see /usr/include/powerpc64le-linux-gnu/bits but no associated /usr/include/bits symbolic link. (The existing directory is in package libc6-dev:ppc64el) * * * Before finding this, I wondered whether --enable-multiarch makes a differen= ce, but it doesn't.=