public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "edo88 at email dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/54353] New: bootstrap-debug-ckovw bootstrap fails because of -fcompare-debug-not-overridden
Date: Wed, 22 Aug 2012 20:38:00 -0000	[thread overview]
Message-ID: <bug-54353-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54353

             Bug #: 54353
           Summary: bootstrap-debug-ckovw bootstrap fails because of
                    -fcompare-debug-not-overridden
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: edo88@email.it


I tried to bootstrap with GCC 4.7 branch with the options indicated below, but
it fails when it configures the 2nd stage for libgcc. I don't have the
config.log but it says as error:

error: unrecognised command line option ‘-fcompare-debug-not-overridden’

configuration:

../gccsrc/configure --enable-languages=c,c++ --prefix=$HOME/buildgcc
--program-suffix=-4.7-svn --with-build-config='bootstrap-debug-lean
bootstrap-debug-lib bootstrap-debug-ckovw'

probably the fault is the gccsrc/config/bootstrap-debug-ckovw.mk file:

FORCE_COMPARE_DEBUG = \
    GCC_COMPARE_DEBUG=$${GCC_COMPARE_DEBUG--fcompare-debug-not-overridden}; \
    export GCC_COMPARE_DEBUG;
POSTSTAGE1_HOST_EXPORTS += $(FORCE_COMPARE_DEBUG)
BASE_TARGET_EXPORTS += $(FORCE_COMPARE_DEBUG)

I can't verify this for the other versions.

>From what I heard in chat it seems that option was never tested it in these
years.


             reply	other threads:[~2012-08-22 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 20:38 edo88 at email dot it [this message]
2021-09-18  7:20 ` [Bug bootstrap/54353] " 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-54353-4@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).