public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107120] [13 Regression] trunk fails to bootstrap on powerpc64le-linux-gnu
Date: Mon, 10 Oct 2022 04:37:21 +0000	[thread overview]
Message-ID: <bug-107120-4-8lyS6lJbrN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107120-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Arseny Solokha <asolokha at gmx dot com> ---
(In reply to Arseny Solokha from comment #2)
> I get the same bootstrap error in libitm while building gcc 13.0.0 20221002
> snapshot (g:d01bd0b0f3b8f4c33c437ff10f0b949200627f56) against glibc 2.36 for
> x86_64.

Jakub in PR107128 comment 4 said enough to resolve this issue for me.

  parent reply	other threads:[~2022-10-10  4:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02  9:01 [Bug bootstrap/107120] New: " doko at gcc dot gnu.org
2022-10-03  9:26 ` [Bug bootstrap/107120] " marxin at gcc dot gnu.org
2022-10-03 18:19 ` asolokha at gmx dot com
2022-10-06  9:55 ` rguenth at gcc dot gnu.org
2022-10-10  4:37 ` asolokha at gmx dot com [this message]
2022-10-24  8:42 ` doko 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-107120-4-8lyS6lJbrN@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).