[Bug fortran/36457] preprocessing: option -idirafter undefined for fortran

2008-12-09 Thread dfranke at gcc dot gnu dot org
--- Comment #5 from dfranke at gcc dot gnu dot org 2008-12-09 19:27 --- Subject: Bug 36457 Author: dfranke Date: Tue Dec 9 19:25:55 2008 New Revision: 142607 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=142607 Log: 2008-12-09 Daniel Franke [EMAIL PROTECTED] PR

[Bug fortran/36457] preprocessing: option -idirafter undefined for fortran

2008-12-09 Thread dfranke at gcc dot gnu dot org
--- Comment #6 from dfranke at gcc dot gnu dot org 2008-12-09 19:29 --- Fixed in trunk. Closing. -- dfranke at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/36457] preprocessing: option -idirafter undefined for fortran

2008-12-03 Thread billingd at gcc dot gnu dot org
--- Comment #1 from billingd at gcc dot gnu dot org 2008-12-03 23:28 --- This is causing testsuite failures and should be fixed. The -idirafter appears to be coming from the cpp section in specs file, while the warning is generated in gcc/opts.c. I can see several possible

[Bug fortran/36457] preprocessing: option -idirafter undefined for fortran

2008-12-03 Thread billingd at gcc dot gnu dot org
--- Comment #2 from billingd at gcc dot gnu dot org 2008-12-04 00:25 --- I can kill this warning if I invoke gfortran with -nostdinc. I would have expected this to be the default. After all, why include C source code or headers in a Fortran file. I will test this patch then ask on

[Bug fortran/36457] preprocessing: option -idirafter undefined for fortran

2008-12-03 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2008-12-04 07:07 --- I can kill this warning if I invoke gfortran with -nostdinc. But won't that break programs which use e.g. include netcdf.inc which is in /usr/include/netcdf.inc ? --

[Bug fortran/36457] preprocessing: option -idirafter undefined for fortran

2008-12-03 Thread dfranke at gcc dot gnu dot org
--- Comment #4 from dfranke at gcc dot gnu dot org 2008-12-04 07:44 --- Thoughts? Make it known to the fortran frontend. I, finally, might find time to get this done this weekend ... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36457