public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Ian Wienand <ianw@gelato.unsw.edu.au>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: driver/9653: invalid detection of "cannot specify -o with -c or -S and multiple compilations" condition
Date: Fri, 14 Mar 2003 02:36:00 -0000	[thread overview]
Message-ID: <20030314023600.12548.qmail@sources.redhat.com> (raw)

The following reply was made to PR driver/9653; it has been noted by GNATS.

From: Ian Wienand <ianw@gelato.unsw.edu.au>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: driver/9653: invalid detection of "cannot specify -o with -c or -S and multiple compilations" condition
Date: Fri, 14 Mar 2003 13:27:47 +1100

 On Fri, Mar 14, 2003 at 02:21:56AM -0000, bangerth@dealii.org wrote:
 >     I can't seem to come up with a simple example to reproduce this. 
 >     Could you check whether this is still happening with a
 >     more recent snapshot of gcc, and possibly extract a
 >     simple procedure how we can reproduce this?
 
 I'm terribly sorry I've been meaning to close this.  It was actually
 that I was using a wrapper script around gcc and used $@ to give gcc
 it's command line.  I didn't realise I actually needed "$@" for it to
 work.  This only shows up in arugments like -MT "a b" or
 -DVER="VERSION 1.0" because the quotes get all lost.
 
 Thanks
 -i


             reply	other threads:[~2003-03-14  2:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14  2:36 Ian Wienand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-14  2:34 bangerth
2003-03-14  2:21 bangerth

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=20030314023600.12548.qmail@sources.redhat.com \
    --to=ianw@gelato.unsw.edu.au \
    --cc=gcc-prs@gcc.gnu.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).