... ... and got the file "penmp" instead of bilin.o ! I do not know if gfortran supports OpenMP, but at least the flag -openmp seems to be interpreted ... with ifort, -xopenmp with SunF95 and -fopenmp with gfortran. When preparing installation procedures for several compilers .... Yes, you're right and you're not the first to point this out. But legacy, ...

... During that time I toyed with Gfortran and put up with the 2 ... The Makefile system does *NOT* work with "gfortran" -- I've tried ... cd /home/coats/Work/Linux2_x86_64gfort; gfortran -c -DIOAPICPL=1 -DAUTO_ARRAYS=1 -DF90...> cd /home/coats/Work/Linux2_x86_64gfort; gfortran -c -DIOAPICPL=1 -DAUTO_ARRAYS=1 -... In GCC (and therefore also in gfortran), -oxxxx means "call the object file...

... got the file "penmp" instead of bilin.o ! I do not know if gfortran supports OpenMP, but at least the flag -openmp seems to ... I used the appropriate openmp flag for gfortran for the first time a couple weeks...Tobias Burns advised me so: F:\gfortran\source>gfortran -o thread -fopenmp ff55.f90 Seems...s anything I miss when I use gfortran it's an IDE and visual debugger...

...... and got the file "penmp" instead of bilin.o ! I do not know if gfortran supports OpenMP, but at least the flag -openmp seems to be ... ifort, -xopenmp with SunF95 and -fopenmp with gfortran. When preparing installation procedures for several compilers and... http://www.g95.org -OR- Support the GNU GFortran Project: http://gcc.gnu.org/fortran/index.html ...

...your compile statement ... and got the file "penmp" instead of bilin.o ! I do not know if gfortran supports OpenMP, but at least the flag -openmp seems to be interpreted as -o "... OpenMP : -openmp with ifort, -xopenmp with SunF95 and -fopenmp with gfortran. When preparing installation procedures for several compilers and architectures, it is easy ...

....Linux2_x86pg # # The following options are NOT library- nor object-compatible; # versions with...>>>> The Makefile system does *NOT* work with "gfortran" -- I've tried ... Actually the Makefile system does not work at all with either ... cd /home/coats/Work/Linux2_x86_64gfort; gfortran -c -DIOAPICPL=1 -DAUTO_ARRAYS=1 ... REMOVE:kargl[60] ~/work/bin/gfortran -c -DIOAPICPL=1 -DAUTO_ARRAYS=1 ...

... The Makefile system does *NOT* work with "gfortran" -- I've tried Actually the Makefile system does not work at all with either FreeBSD'... being from the Mandriva RPM gcc-gfortran-4.2.3-6mnb1. For a ... cd /home/coats/Work/Linux2_x86_64gfort; gfortran -c -DIOAPICPL=1 -DAUTO_ARRAYS=1 -DF90....o REMOVE:kargl[60] ~/work/bin/gfortran -c -DIOAPICPL=1 -DAUTO_ARRAYS=1 -DF90...

...I saw in your compile statement ... and got the file "penmp" instead of bilin.o ! I do not know if gfortran supports OpenMP, but at least the flag -openmp seems to be interpreted as -o "penmp", setting ...Ah, a more recent version uses -fopenmp to enable OpenMP (currently that version is not the default on my system) Regards, Arjen

...statement ... and got the file "penmp" instead of bilin.o ! I do not know if gfortran supports OpenMP, but at least the flag -openmp seems to be interpreted as -o "penmp", setting the output file. Gfortran supports OpenMP, but the flag to enable it is ... But clearly this is all due to the incompetence of the gfortran developers. *rolleyes* -- JayBee

...compile statement ... and got the file "penmp" instead of bilin.o ! I do not know if gfortran supports OpenMP, but at least the flag -openmp seems to be interpreted as -...!" in the original post, I doubt the attitude towards gfortran is going to change too much. FWIW, gfortran is now my main development compiler for the radiative transfer model we work ...