public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	mikerushford@eyes-on-the-skies.org, nobody@gcc.gnu.org
Subject: Re: bootstrap/7800: underscore.c:0: malformed option `-A system=posix'
Date: Fri, 09 May 2003 15:28:00 -0000	[thread overview]
Message-ID: <20030509152806.27512.qmail@sources.redhat.com> (raw)

Synopsis: underscore.c:0: malformed option `-A system=posix'

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Fri May  9 15:28:06 2003
State-Changed-Why:
    Zack posted this question a while ago:
    
    > make[3]: Entering directory `/sda3/objdir/gcc/intl'
     > make[3]: Nothing to be done for `all'.
     > make[3]: Leaving directory `/sda3/objdir/gcc/intl'
     > gcc -c -DIN_GCC    -g  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional   -DHAVE_CONFIG_H    -I. -I. -I/sda3/gcc-3.1.1/gcc-3.1.1/gcc -I/sda3/gcc-3.1.1/gcc-3.1.1/gcc/. -I/sda3/gcc-3.1.1/gcc-3.1.1/gcc/config -I/sda3/gcc-3.1.1/gcc-3.1.1/gcc/../include underscore.c -o underscore.o
     > underscore.c:0: malformed option `-A system=posix'
     
     This error indicates that the bootstrap compiler is picking up the
     specs file for the just-built compiler; naturally this cannot work.  I
     am not sure how it could have happened -- please repeat the command I
     quoted, with an additional -v option tacked on the end, and post the
     output.
     
     zw
    
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7800


             reply	other threads:[~2003-05-09 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09 15:28 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09 22:46 Zack Weinberg
2002-09-01 10:46 Zack Weinberg
2002-09-01 10:26 mikerushford

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=20030509152806.27512.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mikerushford@eyes-on-the-skies.org \
    --cc=nobody@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).