public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andrew at ado dot is-a-geek.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/57125] Build not SMP safe; fails to build bconfig.h
Date: Fri, 29 Aug 2014 20:58:00 -0000	[thread overview]
Message-ID: <bug-57125-4-mWwhR8bO00@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57125-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Oakley <andrew at ado dot is-a-geek.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrew at ado dot is-a-geek.net

--- Comment #5 from Andrew Oakley <andrew at ado dot is-a-geek.net> ---
Created attachment 33419
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33419&action=edit
Possible fix

Attached is a patch which appears to fix this issue for me (on gcc 4.8.3).

In gcc/Makefile.in there is a comment:
# The gengtype generator program is special: Two versions are built.
# One is for the build machine, and one is for the host to allow
# plugins to define their types and generate the supporting GGC
# datastructures and routines with GTY markers.
# The host object files depend on CONFIG_H, and the build objects
# on BCONFIG_H.  For the build objects, add -DGENERATOR_FILE manually,
# the build-%: rule doesn't apply to them.

The change I chose to make swaps the make dependencies around, alternatively
GENERATOR_FILE may defined in the wrong case.  I'm not sure what the right
behaviour is here, or which set of objects is which!


  parent reply	other threads:[~2014-08-29 20:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 12:30 [Bug bootstrap/57125] New: " enrico.scholz at informatik dot tu-chemnitz.de
2013-10-12  5:42 ` [Bug bootstrap/57125] " dirtyepic at gentoo dot org
2014-01-03  9:23 ` vcunat at gmail dot com
2014-03-24 17:59 ` vbraun at physics dot upenn.edu
2014-03-25  4:05 ` dirtyepic at gentoo dot org
2014-08-29 20:58 ` andrew at ado dot is-a-geek.net [this message]
2014-08-29 22:15 ` andrew at ado dot is-a-geek.net
2014-11-05 22:54 ` dev at codyps dot com
2015-03-31  8:07 ` vapier at gentoo dot org
2015-08-10 10:10 ` vapier at gentoo dot org
2021-09-11 22:58 ` pinskia 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-57125-4-mWwhR8bO00@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).