public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/90685] failure of go in gcc-9.1.0 to build in i686-pc-linux-gnu
Date: Sat, 09 Sep 2023 03:36:13 +0000 [thread overview]
Message-ID: <bug-90685-4-5U0kjOYQdf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90685-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90685
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Host| |i?86-*-*
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #2)
> (In reply to Ian Lance Taylor from comment #1)
> > What kind of system are you running on?
> >
> > What is the output of
> > ../gcc-9.1.0/config.guess
> > ?
>
> I just got a similar error on gcc13 on the compile farm; config.guess there
> reports:
>
> $ ../config.guess
> x86_64-pc-linux-gnu
>
> So, confirmed.
Oops wait make that gcc14, not gcc13 (since there isn't even any machine called
gcc13 on the compile farm in the first place)
next prev parent reply other threads:[~2023-09-09 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-90685-4@http.gcc.gnu.org/bugzilla/>
2023-09-09 3:35 ` egallager at gcc dot gnu.org
2023-09-09 3:36 ` egallager at gcc dot gnu.org [this message]
2023-09-10 6:32 ` egallager at gcc dot gnu.org
2024-02-03 11:34 ` brjd_epdjq36 at kygur dot com
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-90685-4-5U0kjOYQdf@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).