public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/7450: Cannot read response file with gcc 2.95-3 and gcc 3.1
Date: Tue, 30 Jul 2002 16:46:00 -0000	[thread overview]
Message-ID: <20020730234601.15014.qmail@sources.redhat.com> (raw)

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

From: Andrew Pinski <pinskia@physics.uc.edu>
To: cheng@powertv.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/7450: Cannot read response file with gcc 2.95-3 and gcc 3.1
Date: Tue, 30 Jul 2002 19:39:29 -0400

 Gcc from FSF does not have this capability but cgywin added it 
 to some of their binaries.
 So this is a feature request, there had been some talk about 
 adding it but nothing I know of have been added yet.
 
 
 Thanks,
 Andrew Pinski
 


             reply	other threads:[~2002-07-30 23:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 16:46 Andrew Pinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-01 20:36 cgf
2002-07-30 16:36 cheng

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=20020730234601.15014.qmail@sources.redhat.com \
    --to=pinskia@physics.uc.edu \
    --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).