This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: target/4789: [DJGPP] preprocessing fortran files by cpp with extension .f
- From: Andris Pavenis <pavenis at latnet dot lv>
- To: neil at gcc dot gnu dot org, bonner at ivp dot bepr dot ethz dot ch, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, toon at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
- Date: Tue, 8 Jan 2002 13:14:43 +0200
- Subject: Re: target/4789: [DJGPP] preprocessing fortran files by cpp with extension .f
- References: <20020108102631.4978.qmail@sources.redhat.com>
On Tuesday 08 January 2002 12:26, neil@gcc.gnu.org wrote:
> Synopsis: [DJGPP] preprocessing fortran files by cpp with extension .f
>
> Responsible-Changed-From-To: toon->unassigned
> Responsible-Changed-By: neil
> Responsible-Changed-When: Tue Jan 8 02:26:30 2002
> Responsible-Changed-Why:
> Not a fortran issue per-se; a target-specific packaging issue
> I think.
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&;
>pr=4789
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)
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)
Andris