public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/4789: [DJGPP] preprocessing fortran files by cpp with extension .f
Date: Tue, 08 Jan 2002 10:46:00 -0000	[thread overview]
Message-ID: <20020108184601.30066.qmail@sources.redhat.com> (raw)

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

From: Neil Booth <neil@daikokuya.demon.co.uk>
To: Andris Pavenis <pavenis@latnet.lv>
Cc: neil@gcc.gnu.org, bonner@ivp.bepr.ethz.ch, gcc-bugs@gcc.gnu.org,
	toon@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: target/4789: [DJGPP] preprocessing fortran files by cpp with extension .f
Date: Tue, 8 Jan 2002 18:42:31 +0000

 Andris Pavenis wrote:-
 
 > The problem appears when -remap is used in specs in cpp_options. cpp_options
 > settings are common for both tradcpp0 and cpp0. For DJGPP we need -remap
 > to avoid need to use changed names of include files (DJGPP can be used under
 > plain MS-DOS when we only have 8+3 filename limitations). -remap is not 
 > recognized by tradcpp0 as valid option. Unfortunatelly tradcpp0 and cpp0 are
 > used also directly in specs not only through trad_capable_cpp (otherwise I 
 > could change there)
 
 Are you saying that getting tradcpp to recognize and ignore -remap
 would fix it?  Or does tradcpp require a -remap implementation?
 
 > I tried to fix that for DJGPP port of gcc-3.0.3, but it required to
 > add options specially for cpp0 only (not for tradcpp0) and to use
 > this new spec where needed (in cp/lang-specs.h and f/lang-specs.h,
 > gcc.c, etc)
 
 What exactly did you do?
 
 Neil.


             reply	other threads:[~2002-01-08 18:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 10:46 Neil Booth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20 16:05 neil
2002-01-08 23:46 Andris Pavenis
2002-01-08  3:16 Andris Pavenis
2002-01-08  2:26 neil

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=20020108184601.30066.qmail@sources.redhat.com \
    --to=neil@daikokuya.demon.co.uk \
    --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).