fj wrote:
> On 19 sep, 15:48, Arjen Markus
wrote:
> >>On 19 sep, 15:27, "Carlie J. Coats"
jyarborough.com> wrote:
>>
>>
>>
>>>>>If you want the whole thing:
>>
>>
>>>-- Carlie- Tekst uit oorspronkelijk bericht niet weergeven -
>>
>>>- Tekst uit oorspronkelijk bericht weergeven -
>>
>>I got it, I compiled the file bilin.f - no problem. Then
>>I compiled it with the option -openmp that 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
>>the output file.
>>
>>Regards,
>>
>>Arjen
>
>
> Amusing : I did exactly the same mistake few month ago when testing
> OpenMP : -openmp with ifort, -xopenmp with SunF95 and -fopenmp with
> gfortran. When preparing installation procedures for several compilers
> and architectures, it is easy to fall down into the trap.
>
> And I needed a quit long period to understand why I got an executable
> file with the name "penmp" :-)
i hate this switch syntax...at a minimum it should require a space,
perhaps a colon for human readability.
--
Gary Scott
mailto:garylscott@sbcglobal dot net
Fortran Library:
http://www.fortranlib.com
Support the Original G95 Project:
http://www.g95.org
-OR-
Support the GNU GFortran Project:
http://gcc.gnu.org/fortran/index.html
If you want to do the impossible, don't hire an expert because he knows
it can't be done.
-- Henry Ford
