public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.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	[thread overview]
Message-ID: <bug-107059-4-dOxXLaqTfx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107059-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(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-3ubuntu1

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 

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 difference,
but it doesn't.

  parent reply	other threads:[~2022-09-28 10:59 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 16:46 [Bug bootstrap/107059] New: " seurer at gcc dot gnu.org
2022-09-27 17:10 ` [Bug bootstrap/107059] " jakub at gcc dot gnu.org
2022-09-27 17:28 ` marxin at gcc dot gnu.org
2022-09-27 17:37 ` jakub at gcc dot gnu.org
2022-09-27 18:40 ` seurer at gcc dot gnu.org
2022-09-27 18:50 ` jakub at gcc dot gnu.org
2022-09-27 18:52 ` seurer at gcc dot gnu.org
2022-09-27 19:13 ` jakub at gcc dot gnu.org
2022-09-27 19:20 ` seurer at gcc dot gnu.org
2022-09-27 19:26 ` jakub at gcc dot gnu.org
2022-09-27 19:59 ` seurer at gcc dot gnu.org
2022-09-27 20:22 ` jakub at gcc dot gnu.org
2022-09-28  9:45 ` tnfchris at gcc dot gnu.org
2022-09-28  9:46 ` jakub at gcc dot gnu.org
2022-09-28 10:12 ` jakub at gcc dot gnu.org
2022-09-28 10:59 ` burnus at gcc dot gnu.org [this message]
2022-09-28 11:18 ` burnus at gcc dot gnu.org
2022-09-28 11:26 ` burnus at gcc dot gnu.org
2022-09-28 11:37 ` jakub at gcc dot gnu.org
2022-09-28 12:58 ` burnus at gcc dot gnu.org
2022-09-28 13:10 ` burnus at gcc dot gnu.org
2022-09-28 13:12 ` jakub at gcc dot gnu.org
2022-09-28 17:16 ` joseph at codesourcery dot com
2022-09-28 18:40 ` burnus at gcc dot gnu.org
2022-09-28 18:47 ` jakub at gcc dot gnu.org
2022-09-28 18:57 ` burnus at gcc dot gnu.org
2022-09-28 19:04 ` jakub at gcc dot gnu.org
2022-09-28 19:20 ` manuel.lauss at googlemail dot com
2022-09-29  8:07 ` rguenth at gcc dot gnu.org
2022-09-29 10:06 ` cvs-commit at gcc dot gnu.org
2022-09-29 10:14 ` jakub at gcc dot gnu.org
2022-10-03 15:29 ` seurer at gcc dot gnu.org
2022-10-03 15:33 ` jakub at gcc dot gnu.org
2022-10-07  7:00 ` cvs-commit at gcc dot gnu.org
2022-10-07  7:00 ` cvs-commit at gcc dot gnu.org
2022-10-07  7:01 ` jakub at gcc dot gnu.org

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=bug-107059-4-dOxXLaqTfx@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).