On Sep 19, 9:12 pm, Gary Scott
sbcglobal.net> wrote:> 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.
Yes, you're right and you're not the first to point this out.
But legacy, oh legacy... We Fortran-ers know all about it, no? :-)
Gr.
Steven
