When invoking gfortran to compile some fortran code with C preprocessor commands in it and using the .F file extension to ensure that the code is passed though the C pre-processor and error occurs with cc1 The command is: gfortran -c -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fno-underscoring -DNOUNIRAS -DNONAMELISTS -I../f77_param filterpl.F and the error is: cc1: error: unrecognized command line option "-fno-underscoring" This error did not occur when using an older gfortran version. cpp won't recognise "-fno-underscoring" but the old gfortran presumably did not pass this to cpp whereas the newer version does. I have a workround which involves invoking cpp seperately on the file excluding the "-fno-underscoring" and the compiling the output from this but it would be good to have the old functionality back. Kevin
Works with 4.3.
Could you provide some more details, especially about your gfortran version. The problem is that using: $ gfortran-4.1 -fno-underscoring aa.F $ gfortran-4.2 -fno-underscoring aa.F $ gfortran-4.3 -fno-underscoring aa.F $ gfortran -fno-underscoring aa.F # 4.4.0 of today all work. Where did you obtain gfortran and GCC? Which system are you on? If I call gcc (4.1 to 4.4) with -fno-underscoring then I get the warning: cc1: warning: command line option "-fno-underscoring" is valid for Fortran but not for C Therefore, I wonder whether you are either using an ancient version of gfortran or that for some reason your new gfortran calls an older version of gcc.
Subject: RE: gfrotran and cc1 error Hi Thanks for the response. I was actually installing software on someone else's system (with their permission) which was an apple machine. I will check the version of gcc and the rest of the installation. Cheers Kevin -----Original Message----- From: burnus at gcc dot gnu dot org [mailto:gcc-bugzilla@gcc.gnu.org] Sent: 23 May 2008 18:49 To: kih@mail.nerc-essc.ac.uk Subject: [Bug fortran/36309] gfrotran and cc1 error ------- Comment #2 from burnus at gcc dot gnu dot org 2008-05-23 17:49 ------- Could you provide some more details, especially about your gfortran version. The problem is that using: $ gfortran-4.1 -fno-underscoring aa.F $ gfortran-4.2 -fno-underscoring aa.F $ gfortran-4.3 -fno-underscoring aa.F $ gfortran -fno-underscoring aa.F # 4.4.0 of today all work. Where did you obtain gfortran and GCC? Which system are you on? If I call gcc (4.1 to 4.4) with -fno-underscoring then I get the warning: cc1: warning: command line option "-fno-underscoring" is valid for Fortran but not for C Therefore, I wonder whether you are either using an ancient version of gfortran or that for some reason your new gfortran calls an older version of gcc.
Subject: RE: gfrotran and cc1 error Hi 'gfortran -v' and 'gcc -v' report: gfortran -v Using built-in specs. Target: powerpc-apple-darwin8 Configured with: /Builds/apple/gcc_42-5531/obj/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/usr/share/man --enable-languages=c,objc,c++,obj-c++,fortran --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-gxx-include-dir=/usr/include/c++/4.0.0 --with-slibdir=/usr/lib --build=i686-apple-darwin8 --program-prefix= --host=powerpc-apple-darwin8 --target=powerpc-apple-darwin8 Thread model: posix gcc version 4.2.1 (Apple Inc. build 5531) gcc -v Using built-in specs. Target: powerpc-apple-darwin8 Configured with: /Builds/apple/gcc_42-5531/obj/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/usr/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-gxx-include-dir=/usr/include/c++/4.0.0 --with-slibdir=/usr/lib --build=i686-apple-darwin8 --program-prefix= --host=powerpc-apple-darwin8 --target=powerpc-apple-darwin8 Thread model: posix gcc version 4.2.1 (Apple Inc. build 5531) Kevin -----Original Message----- From: burnus at gcc dot gnu dot org [mailto:gcc-bugzilla@gcc.gnu.org] Sent: 23 May 2008 18:49 To: kih@mail.nerc-essc.ac.uk Subject: [Bug fortran/36309] gfrotran and cc1 error ------- Comment #2 from burnus at gcc dot gnu dot org 2008-05-23 17:49 ------- Could you provide some more details, especially about your gfortran version. The problem is that using: $ gfortran-4.1 -fno-underscoring aa.F $ gfortran-4.2 -fno-underscoring aa.F $ gfortran-4.3 -fno-underscoring aa.F $ gfortran -fno-underscoring aa.F # 4.4.0 of today all work. Where did you obtain gfortran and GCC? Which system are you on? If I call gcc (4.1 to 4.4) with -fno-underscoring then I get the warning: cc1: warning: command line option "-fno-underscoring" is valid for Fortran but not for C Therefore, I wonder whether you are either using an ancient version of gfortran or that for some reason your new gfortran calls an older version of gcc.
(In reply to comment #4) > 'gfortran -v' and 'gcc -v' report Those look like Apple build (I didn't know they had Fortran in official builds); did you install them or do they come with the system? Otherwise, it looks like an issue specific to Apple builds if that's what they are.
Subject: RE: gfortran and cc1 error The distribution came from: http://r.research.att.com/tools/ so I guess I should take it up with them. Regards Kevin -----Original Message----- From: fxcoudert at gcc dot gnu dot org [mailto:gcc-bugzilla@gcc.gnu.org] Sent: 26 May 2008 16:45 To: kih@mail.nerc-essc.ac.uk Subject: [Bug fortran/36309] gfortran and cc1 error ------- Comment #5 from fxcoudert at gcc dot gnu dot org 2008-05-26 15:45 ------- (In reply to comment #4) > 'gfortran -v' and 'gcc -v' report Those look like Apple build (I didn't know they had Fortran in official builds); did you install them or do they come with the system? Otherwise, it looks like an issue specific to Apple builds if that's what they are. -- fxcoudert at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fxcoudert at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36309 ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter.
What the issue is that the C compiler was not configured with fortran compiler so they don't ignore the fortran options but then the fortran compiler was configured separately. So this is invalid and really an issue with how cc1 was built.