* [Bug go/90685] failure of go in gcc-9.1.0 to build in i686-pc-linux-gnu
[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
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: egallager at gcc dot gnu.org @ 2023-09-09 3:35 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90685
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
CC| |egallager at gcc dot gnu.org
Ever confirmed|0 |1
Last reconfirmed| |2023-09-09
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
(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.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug go/90685] failure of go in gcc-9.1.0 to build in i686-pc-linux-gnu
[not found] <bug-90685-4@http.gcc.gnu.org/bugzilla/>
2023-09-09 3:35 ` [Bug go/90685] failure of go in gcc-9.1.0 to build in i686-pc-linux-gnu egallager at gcc dot gnu.org
@ 2023-09-09 3:36 ` egallager at gcc dot gnu.org
2023-09-10 6:32 ` egallager at gcc dot gnu.org
2024-02-03 11:34 ` brjd_epdjq36 at kygur dot com
3 siblings, 0 replies; 4+ messages in thread
From: egallager at gcc dot gnu.org @ 2023-09-09 3:36 UTC (permalink / raw)
To: gcc-bugs
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)
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug go/90685] failure of go in gcc-9.1.0 to build in i686-pc-linux-gnu
[not found] <bug-90685-4@http.gcc.gnu.org/bugzilla/>
2023-09-09 3:35 ` [Bug go/90685] failure of go in gcc-9.1.0 to build in i686-pc-linux-gnu egallager at gcc dot gnu.org
2023-09-09 3:36 ` egallager at gcc dot gnu.org
@ 2023-09-10 6:32 ` egallager at gcc dot gnu.org
2024-02-03 11:34 ` brjd_epdjq36 at kygur dot com
3 siblings, 0 replies; 4+ messages in thread
From: egallager at gcc dot gnu.org @ 2023-09-10 6:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90685
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #3)
> (In reply to Eric Gallager from comment #2)
> > 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)
Also happens on the machine called "gcc45" on the compile farm, where
../config.guess reports i686-pc-linux-gnu
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug go/90685] failure of go in gcc-9.1.0 to build in i686-pc-linux-gnu
[not found] <bug-90685-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2023-09-10 6:32 ` egallager at gcc dot gnu.org
@ 2024-02-03 11:34 ` brjd_epdjq36 at kygur dot com
3 siblings, 0 replies; 4+ messages in thread
From: brjd_epdjq36 at kygur dot com @ 2024-02-03 11:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90685
Brjd <brjd_epdjq36 at kygur dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |brjd_epdjq36 at kygur dot com
--- Comment #5 from Brjd <brjd_epdjq36 at kygur dot com> ---
I got the same error on x86_64-pc-linux-gnu at libgo/libgotool.a :
go1: error: ‘-fsplit-stack’ currently only supported on GNU/Linux
go1: error: ‘-fsplit-stack’ is not supported by this compiler configuration
I disable the build since it stops at gotools. It is not quite clear if it is
supported in all glibc versions, whether -fsplit-stack is needed for the gccgo
build or not, and I see that it is disabled for non-glibcs in the gnu.h header
because of -fsplit-stack issues which is correct of course.
I guess these problems may be serious, e.g. possible memory corruption,
segfaults etc. But I was unable to find reliable information in the gcc docs. I
would suggest if the checks of compatibility are made at the very beginning
when the build is configured initially, so that users know if the go build is
supported on their system or not.
^ permalink raw reply [flat|nested] 4+ messages in thread