MadGraph5_aMC@NLO

undefined reference to `_gfortran_transfer_real_write'

Asked by Stefania Spagnolo

Hi all,
I'm experiencing a setup problem (I believe) when trying to generate Zbb events at NLO at LHC with
generate p p > b b~ Z [QCD]
I've set the fortran compiler to /afs/cern.ch/sw/lcg/external/gcc/4.7.0/x86_64-slc5-gcc47-opt/bin/gfortran
but I get a long list of errors like:

undefined reference to `_gfortran_transfer_real/character/int_write'

after

     /afs/cern.ch/sw/lcg/external/gcc/4.7.0/x86_64-slc5-gcc47-opt/bin/gfortran -O -fno-automatic -ffixed-line-length-132 -o test_ME symmetry_fks_test_ME.o parton_lum_1.o parton_lum_2.o parton_lum_3.o parton_lum_4.o parton_lum_5.o parton_lum_6.o parton_lum_7.o parton_lum_8.o parton_lum_9.o parton_lum_chooser.o matrix_1.o matrix_2.o matrix_3.o matrix_4.o matrix_5.o matrix_6.o matrix_7.o matrix_8.o matrix_9.o real_me_chooser.o fks_inc_chooser.o leshouche_inc_chooser.o genps_fks.o setcuts.o setscales.o born.o sborn_sf.o b_sf_001.o b_sf_002.o b_sf_003.o b_sf_004.o b_sf_005.o b_sf_006.o b_sf_007.o b_sf_008.o fks_Sij.o trapfpe.o fastjetfortran_madfks.o ktclusdble.o fks_singular.o montecarlocounter.o reweight_xsec.o boostwdir2.o BinothLHADummy.o cuts.o -L../../lib/ -ldhelas -lgeneric -lmodel -lpdf -Wl,-rpath,/afs/cern.ch/sw/lcg/external/fastjet/3.0.3/x86_64-slc5-gcc43-opt/lib -lm -L/afs/cern.ch/sw/lcg/external/fastjet/3.0.3/x86_64-slc5-gcc43-opt/lib -lfastjettools -lfastjet -lfastjetplugins -lsiscone_spherical -lsiscone -L/afs/cern.ch/sw/lcg/contrib/gcc/4.3.5/x86_64-slc5-gcc34-opt/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.3.5 -L/afs/cern.ch/sw/lcg/contrib/gcc/4.3.5/x86_64-slc5-gcc34-opt/bin/../lib/gcc -L/afs/cern.ch/sw/lcg/contrib/gcc/4.3.5/x86_64-slc5-gcc34-opt/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.3.5/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/afs/cern.ch/sw/lcg/contrib/gcc/4.3.5/x86_64-slc5-gcc34-opt/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.3.5/../../.. -lgfortranbegin -lgfortran -lm -lstdc++
     symmetry_fks_test_ME.o: In function `MAIN__':
     symmetry_fks_test_ME.f:(.text+0x4c): undefined reference to `_gfortran_transfer_character_write'
     symmetry_fks_test_ME.f:(.text+0x95): undefined reference to `_gfortran_transfer_character_write'
     symmetry_fks_test_ME.f:(.text+0x13b): undefined reference to `_gfortran_transfer_character_write'
     symmetry_fks_test_ME.f:(.text+0x1e1): undefined reference to `_gfortran_transfer_character_write'
     symmetry_fks_test_ME.f:(.text+0x29b): undefined reference to `_gfortran_transfer_character_write'
     symmetry_fks_test_ME.o:symmetry_fks_test_ME.f:(.text+0x381): more undefined references to `_gfortran_transfer_character_write' follow
     symmetry_fks_test_ME.o: In function `MAIN__':
     symmetry_fks_test_ME.f:(.text+0x4cd): undefined reference to `_gfortran_transfer_integer_write'
     symmetry_fks_test_ME.f:(.text+0x516): undefined reference to `_gfortran_transfer_character_write'

It is not clear to me how to fix the problem - thanks for any suggestion.
Best regards,
Stefania

Question information

Language:
English Edit question
Status:
Expired
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Valentin Hirschi (valentin-hirschi) said : 		#1

Dear Stefania,

We have already seen similar issues (but on the MadLoop side) and it turned out to be a bug in one of the native library of the compiler /afs/cern.ch/sw/lcg/external/gcc/4.7.0/x86_64-slc5-gcc47-opt/bin/gfortran you used.
The error is simply triggered by fortran write(*,*) statements of a quadruple precision variable, which is of course not essential for running. A work-around has been implemented already in the development version but not yet in the public one I assume you are using.

The unexpected thing is that it seems the compilation failure seems to originate from symmetry_fks_test_ME.f where I don't expect quadruple precision variables to be used. In order to have a better look, could you tell me what version of the MG code you are using, so that I can have reproduce the exact same files you produced for that process. In the meantime, try commenting out any write(*,*) statement you find in the files pointed out by the compiler and let me know if this helps.

Revision history for this message
Stefano Frixione (stefano-frixione) said : 		#2

Hi Stefania,
the gfortran you use is that relevant to SLC5 machines.
Most of lxplus and related nodes have been upgraded to SLC6.
Are you sure you're running on an SLC5 machine?
Best, Stefano

Revision history for this message
Stefania Spagnolo (stefania-a-spagnolo) said : 		#3

Dear Stefano, Valentin and all,
thanks for your answer; it turned out that I had an inconsistent (in terms
of the gcc version) choice of libraries.
After fixing that we didn't see the compilation failure anymore.
Best regards,
Stefania

On Tue, Jul 9, 2013 at 1:51 PM, Stefano Frixione <
<email address hidden>> wrote:

> Your question #232112 on MadGraph5 changed:
> https://answers.launchpad.net/madgraph5/+question/232112
>
> Status: Needs information => Answered
>
> Stefano Frixione proposed the following answer:
> Hi Stefania,
> the gfortran you use is that relevant to SLC5 machines.
> Most of lxplus and related nodes have been upgraded to SLC6.
> Are you sure you're running on an SLC5 machine?
> Best, Stefano
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/madgraph5/+question/232112/+confirm?answer_id=1
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/madgraph5/+question/232112
>
> You received this question notification because you asked the question.
>

Revision history for this message
Launchpad Janitor (janitor) said : 		#4

This question was expired because it remained in the 'Open' state without activity for the last 15 days.