Problems with the -J option (Cygwin)

[Angelo Graziosi <Angelo dot Graziosi at roma1 dot infn dot it>]

I have observed the following on Cygwin (but, perhaps, it is a general
problem), with GFortran built myself:

$ gfortran -v
Using built-in specs.
Target: i686-pc-cygwin
Configured with: /home/Angelo/Downloads/GFortran/gcc/configure
--prefix=/usr/loc
al/gfortran --enable-threads=posix --enable-sjlj-exceptions
--with-system-zlib -
-disable-nls --disable-libmudflap --enable-version-specific-runtime-libs
--witho
ut-included-gettext --disable-shared --enable-languages=c,fortran
Thread model: posix
gcc version 4.3.0 20061121 (experimental)

using http://quatramaran.ens.fr/~coudert/gfortran/gcc-svn-light.tar.bz2,
timestaps Nov 21 04:14.



I have an application that I build with

gfc -Wall -fno-automatic -J../module -I../module
-I/home/Angelo/Applications/meg/include  -O2 -c rchps95.F95 -o
rchps95-gfc.o

I use the -J../module and -I../module options so that all *.mod file are
in ../module and are found there.

With the above built of GFortran, the *.o file is not created! (so it is
impossible to complete the build of that application).


I have reproduced the thing with this very simple test case:

cat hello.F95
program hello
  implicit none
  write(*,*) 'Hello!'
end program hello

gfc -J../module  -c hello.F95 -o hello.o

The hello.o is not creted. Obviously removing the -J opt. all works fine
and all works fine also with a previous build I did: Nov 06 2006!

So it seems a problem with recent source.


   Angelo