[Developers] Detection of gfortran
Jian Tao
jtao at cct.lsu.edu
Wed Nov 7 01:01:56 CST 2007
As a user, I link gfortran myself, but it should be
auto-detected. I will take a look.
Regards,
Jian
Ian Hinder wrote:
> Jian Tao wrote:
>> Forgot to link -lgfortran ?
>
> So am I supposed modify my LDFLAGS variable? Shouldn't this be
> autodetected?
>
>> Regards,
>> Jian
>>
>> Ian Hinder wrote:
>>> Hi,
>>>
>>> I am trying to use Cactus (latest development version) on my laptop with
>>> gcc and gfortran. The laptop is running Ubuntu 7.10. In my config file
>>> I have
>>>
>>> F90=gfortran
>>> F77=gfortran
>>> HDF5=yes
>>> MPI=MPICH
>>> OPTIMISE=no
>>>
>>> The compilation stage fails with missing symbols, for example
>>>
>>> /home/ian/work/Cactus/configs/wavetoy/lib/libthorn_IDScalarWaveMoL.a(initialdata.F77.o):
>>> In function `idscalarwavemol_initialda
>>> ta_':
>>> initialdata.f:(.text+0xd05): undefined reference to `_gfortran_pow_r8_i4'
>>> i
>>>
>>> So it looks like for some reason there is a gfortran library which is
>>> not being picked up. In the
>>>
>>> Cactus/lib/make/known-architectures/linux
>>>
>>> file, I notice the line
>>>
>>> elif test "`$F90 -dumpversion 2>&1 | grep 'GNU Fortran 95'`" ; then
>>>
>>> to detect the fortran compiler. Running
>>>
>>> gfortran -dumpversion
>>>
>>> I get
>>>
>>> GNU Fortran (GCC) 4.2.1 (Ubuntu 4.2.1-5ubuntu4)
>>>
>>> so it is not reporting itself as "GNU Fortran 95". Should it be? If I
>>> modify the detection script to search for "GNU Fortran" instead,
>>> reconfigure and relink, everything works. So I have two questions:
>>>
>>> (1) Should the known architectures file be modified to search just for
>>> "GNU Fortran"?
>>>
>>> (2) Why was there no error message that the compiler was not recognized
>>> correctly?
>>>
>> _______________________________________________
>> Developers mailing list
>> Developers at cactuscode.org
>> http://www.cactuscode.org/mailman/listinfo/developers
>
>
More information about the Developers
mailing list