From: howarth@bromo.msbb.uc.edu (Jack Howarth)
To: howarth@bromo.msbb.uc.edu, pinskia@physics.uc.edu
Cc: gcc@gcc.gnu.org, schwab@suse.de
Subject: Re: strange error on gcc 4.1.0
Date: Sat, 30 Jul 2005 16:15:00 -0000 [thread overview]
Message-ID: <20050730161159.EE64F1DC167@bromo.msbb.uc.edu> (raw)
Here is another posting which describes the problem a little clearer...
http://lists.apple.com/archives/darwin-development/2003/Jun/msg00000.html
So gcc needs to be fixed to not misparse -bundle, when it is the first
argument to gcc, as being the "-b Machine" target option.
Shouldn't the fix be fairly simple? Just requiring that the
code that recognizes the -b flag require a trailing space after
the -b flag...otherwise it passes over it so that -bundle could be
recognized?
Jack
next reply other threads:[~2005-07-30 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 16:15 Jack Howarth [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-30 16:22 Jack Howarth
2005-07-30 15:55 Jack Howarth
2005-07-30 16:09 ` Andrew Pinski
2005-07-31 4:44 ` Mike Stump
2005-07-30 13:42 Jack Howarth
2005-07-30 15:18 ` Andrew Pinski
2005-07-30 8:47 Jack Howarth
2005-07-30 9:50 ` Andreas Schwab
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=20050730161159.EE64F1DC167@bromo.msbb.uc.edu \
--to=howarth@bromo.msbb.uc.edu \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
--cc=schwab@suse.de \
/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).