public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "svante.signell at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/104290] [12 Regression] trunk 20220126 fails to build libgo on i686-gnu
Date: Wed, 09 Feb 2022 22:11:12 +0000	[thread overview]
Message-ID: <bug-104290-4-S6mYxLScam@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104290-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Svante Signell <svante.signell at gmail dot com> ---
> If you make all-target-libgo all dependencies are respected.

Sorry but that is not how things work:
all-target-libgo: maybe-all-target-libffi
is outside any conditionals, but 
all-target-libgo: maybe-all-target-libbacktrace
all-target-libgo: maybe-all-target-libatomic
are inside the conditional
@unless gcc-bootstrap
@endunless gcc-bootstrap
in src/Makefile.in :(
and therefore not included in the generated build/Makefile.

The unless/endunless condition does not seem to be met in the generated
build/Makefile.

As far as I've searched, no understandable explanation of 
@unless/@endunless gcc-bootstrap is found in the gcc-12 tree either. No
explanation in Makefile.tpl

I found only a commit for binutils-gdb:
https://isrc.iscas.ac.cn/gitlab/mirrors/sourceware.org/git_binutils-gdb/-/commit/4119873a48042e532f7485b84cca83ea0bf1fcf6
but that one is not very informative :(

moving
all-target-libgo: maybe-all-target-libbacktrace
all-target-libgo: maybe-all-target-libatomic
next to
all-target-libgo: maybe-all-target-libffi
in Makefile.in all works fine.

Generating a new version of Makefile.in by:
(cd source; autogen Makefile.def)
does not solve the problem: the same buggy build/Makefile is created.

This is not a Debian problem, it is an upstream bug, as far as I've found.

It seems like everything not linux-any is left unsupported, not a nice
situation... Your choice!

And patching gnu.h to not support split-stack any longer is really not nice.
Don't you ever build gcc for GNU/Hurd? If not maybe I can help to set up such a
build environment. Just let me know!!

Thanks!

  parent reply	other threads:[~2022-02-09 22:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30 13:38 [Bug go/104290] New: " doko at debian dot org
2022-01-31  8:21 ` [Bug go/104290] " rguenth at gcc dot gnu.org
2022-02-03 15:16 ` svante.signell at gmail dot com
2022-02-06 11:43 ` svante.signell at gmail dot com
2022-02-08 17:08 ` svante.signell at gmail dot com
2022-02-08 17:29 ` schwab@linux-m68k.org
2022-02-08 17:50 ` ian at airs dot com
2022-02-08 19:37 ` svante.signell at gmail dot com
2022-02-08 19:44 ` schwab@linux-m68k.org
2022-02-09 22:11 ` svante.signell at gmail dot com [this message]
2022-02-17 17:30 ` cvs-commit at gcc dot gnu.org
2022-02-17 22:20 ` svante.signell at gmail dot com
2022-02-17 22:21 ` svante.signell at gmail dot com
2022-02-17 22:22 ` svante.signell at gmail dot com
2022-02-17 22:23 ` svante.signell at gmail dot com
2022-02-17 22:23 ` svante.signell at gmail dot com
2022-02-17 22:24 ` svante.signell at gmail dot com
2022-02-17 22:25 ` svante.signell at gmail dot com
2022-02-17 22:25 ` svante.signell at gmail dot com
2022-02-17 22:26 ` svante.signell at gmail dot com
2022-02-17 22:41 ` svante.signell at gmail dot com
2022-02-17 22:45 ` svante.signell at gmail dot com
2022-02-18 18:28 ` ian at airs dot com
2022-02-18 22:57 ` ian at airs dot com
2022-02-18 23:33 ` [Bug go/104290] [12 Regression] trunk 20220214 " cvs-commit at gcc dot gnu.org
2022-02-19  9:40 ` svante.signell at gmail dot com
2022-02-20 20:15 ` ian at airs dot com
2022-02-21 16:05 ` svante.signell at gmail dot com
2022-02-21 16:23 ` ian at airs dot com
2022-05-06  8:32 ` [Bug go/104290] [12/13 " jakub at gcc dot gnu.org
2022-07-26 13:01 ` rguenth at gcc dot gnu.org
2022-07-29  6:31 ` pinskia at gcc dot gnu.org
2023-02-21 14:59 ` rguenth at gcc dot gnu.org
2023-02-21 17:00 ` ian at airs dot com
2023-03-15 16:27 ` svante.signell at gmail dot com
2023-05-08 12:23 ` [Bug go/104290] [12/13/14 " rguenth 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-104290-4-S6mYxLScam@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).