From kellerma at aei.mpg.de Tue Nov 6 12:33:47 2007 From: kellerma at aei.mpg.de (Thorsten Kellermann) Date: Tue, 06 Nov 2007 19:33:47 +0100 Subject: [Developers] error message Message-ID: <4730B38B.5060909@aei.mpg.de> Can somebody explain me what this debugger message means ? Thorsten warning: core file may not match specified executable file. Reading symbols from shared object read from target memory...done. Loaded system supplied DSO at 0x406000 Core was generated by `../../exe/cactus_Whisky2D_RNSID_new GRRNSID_50s_axis_rot_0.67.par'. Program terminated with signal 11, Segmentation fault. warning: svr4_current_sos: Can't read pathname for load map: Input/output error Reading symbols from /usr/lib/libhdf5.so.0...done. Loaded symbols for /usr/lib/libhdf5.so.0 Reading symbols from /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/libimf.so...done. Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/libimf.so Reading symbols from /lib/libm.so.6...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/mkl8.1.1/lib/32/libmkl.so...done. Loaded symbols for /opt/net/afs/apps/intel/mkl8.1.1/lib/32/libmkl.so Reading symbols from /usr/lib/lam/liblammpi++.so.0...done. Loaded symbols for /usr/lib/lam/liblammpi++.so.0 Reading symbols from /usr/lib/lam/libmpi.so.0...done. Loaded symbols for /usr/lib/lam/libmpi.so.0 Reading symbols from /usr/lib/lam/liblam.so.0...done. Loaded symbols for /usr/lib/lam/liblam.so.0 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/libpthread.so.0...done. Loaded symbols for /lib/libpthread.so.0 Reading symbols from /usr/lib/libaio.so.1...done. Loaded symbols for /usr/lib/libaio.so.1 Reading symbols from /lib/libutil.so.1...done. Loaded symbols for /lib/libutil.so.1 Reading symbols from /lib/libcrypt.so.1...done. Loaded symbols for /lib/libcrypt.so.1 Reading symbols from /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/libifcore.so.5...done. Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/libifcore.so.5 Reading symbols from /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/libsvml.so...done. Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/libsvml.so Reading symbols from /usr/lib/libstdc++.so.6...done. Loaded symbols for /usr/lib/libstdc++.so.6 Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/libcxaguard.so.5...done. Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/libcxaguard.so.5 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/libssl.so.6...done. Loaded symbols for /lib/libssl.so.6 Reading symbols from /lib/libcrypto.so.6...done. Loaded symbols for /lib/libcrypto.so.6 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/libirc.so...done. Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/libirc.so Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/libguide.so...done. Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/libguide.so Reading symbols from /usr/lib/libgssapi_krb5.so.2...done. Loaded symbols for /usr/lib/libgssapi_krb5.so.2 Reading symbols from /usr/lib/libkrb5.so.3...done. Loaded symbols for /usr/lib/libkrb5.so.3 Reading symbols from /lib/libcom_err.so.2...done. Loaded symbols for /lib/libcom_err.so.2 Reading symbols from /usr/lib/libk5crypto.so.3...done. Loaded symbols for /usr/lib/libk5crypto.so.3 Reading symbols from /lib/libresolv.so.2...done. Loaded symbols for /lib/libresolv.so.2 Reading symbols from /usr/lib/libkrb5support.so.0...done. Loaded symbols for /usr/lib/libkrb5support.so.0 Reading symbols from /lib/libnss_files.so.2...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /lib/libnss_nis.so.2...done. Loaded symbols for /lib/libnss_nis.so.2 Reading symbols from /lib/libnsl.so.1...done. Loaded symbols for /lib/libnsl.so.1 #0 0x00d4aa0b in _int_malloc () from /usr/lib/lam/libmpi.so.0 From schnetter at cct.lsu.edu Tue Nov 6 13:20:42 2007 From: schnetter at cct.lsu.edu (Erik Schnetter) Date: Tue, 6 Nov 2007 13:20:42 -0600 Subject: [Developers] error message In-Reply-To: <4730B38B.5060909@aei.mpg.de> References: <4730B38B.5060909@aei.mpg.de> Message-ID: <35DDBF1A-D8E1-4BDB-9EC8-80CE4F0FB3DD@cct.lsu.edu> On Nov 6, 2007, at 12:33:47, Thorsten Kellermann wrote: > Can somebody explain me > what this debugger message means ? > > Thorsten Hi Thorsten, I think you have multiple issues at the same time: > warning: core file may not match specified executable file. This means that you rebuilt the executable since the core file was generated, or that you are using a different set of shared libraries for debugging than you used for running. This happens especially if the front end has different software installed than compute nodes. > Reading symbols from shared object read from target memory...done. > Loaded system supplied DSO at 0x406000 > Core was generated by `../../exe/cactus_Whisky2D_RNSID_new > GRRNSID_50s_axis_rot_0.67.par'. > Program terminated with signal 11, Segmentation fault. This means that you either have an array/pointer error, or that you ran out of memory. > warning: svr4_current_sos: Can't read pathname for load map: > Input/output error That probably means that some library or support file was not found. It could again be caused by an installation inconsistency. -erik > Reading symbols from /usr/lib/libhdf5.so.0...done. > Loaded symbols for /usr/lib/libhdf5.so.0 > Reading symbols from > /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/ > libimf.so...done. > Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/libimf.so > Reading symbols from /lib/libm.so.6...done. > Loaded symbols for /lib/libm.so.6 > Reading symbols from > /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/mkl8.1.1/lib/32/ > libmkl.so...done. > Loaded symbols for /opt/net/afs/apps/intel/mkl8.1.1/lib/32/libmkl.so > Reading symbols from /usr/lib/lam/liblammpi++.so.0...done. > Loaded symbols for /usr/lib/lam/liblammpi++.so.0 > Reading symbols from /usr/lib/lam/libmpi.so.0...done. > Loaded symbols for /usr/lib/lam/libmpi.so.0 > Reading symbols from /usr/lib/lam/liblam.so.0...done. > Loaded symbols for /usr/lib/lam/liblam.so.0 > Reading symbols from /lib/libdl.so.2...done. > Loaded symbols for /lib/libdl.so.2 > Reading symbols from /lib/libpthread.so.0...done. > Loaded symbols for /lib/libpthread.so.0 > Reading symbols from /usr/lib/libaio.so.1...done. > Loaded symbols for /usr/lib/libaio.so.1 > Reading symbols from /lib/libutil.so.1...done. > Loaded symbols for /lib/libutil.so.1 > Reading symbols from /lib/libcrypt.so.1...done. > Loaded symbols for /lib/libcrypt.so.1 > Reading symbols from > /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/ > libifcore.so.5...done. > Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/ > libifcore.so.5 > Reading symbols from > /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/ > libsvml.so...done. > Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/libsvml.so > Reading symbols from /usr/lib/libstdc++.so.6...done. > Loaded symbols for /usr/lib/libstdc++.so.6 > Reading symbols from /lib/libgcc_s.so.1...done. > Loaded symbols for /lib/libgcc_s.so.1 > Reading symbols from > /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/ > libcxaguard.so.5...done. > Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/ > libcxaguard.so.5 > Reading symbols from /lib/libc.so.6...done. > Loaded symbols for /lib/libc.so.6 > Reading symbols from /lib/libssl.so.6...done. > Loaded symbols for /lib/libssl.so.6 > Reading symbols from /lib/libcrypto.so.6...done. > Loaded symbols for /lib/libcrypto.so.6 > Reading symbols from /usr/lib/libz.so.1...done. > Loaded symbols for /usr/lib/libz.so.1 > Reading symbols from > /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/ > libirc.so...done. > Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/libirc.so > Reading symbols from /lib/ld-linux.so.2...done. > Loaded symbols for /lib/ld-linux.so.2 > Reading symbols from > /afs/aei-potsdam.mpg.de/i386_linux26/apps/intel/compiler91/lib/ > libguide.so...done. > Loaded symbols for /opt/net/afs/apps/intel/compiler91/lib/libguide.so > Reading symbols from /usr/lib/libgssapi_krb5.so.2...done. > Loaded symbols for /usr/lib/libgssapi_krb5.so.2 > Reading symbols from /usr/lib/libkrb5.so.3...done. > Loaded symbols for /usr/lib/libkrb5.so.3 > Reading symbols from /lib/libcom_err.so.2...done. > Loaded symbols for /lib/libcom_err.so.2 > Reading symbols from /usr/lib/libk5crypto.so.3...done. > Loaded symbols for /usr/lib/libk5crypto.so.3 > Reading symbols from /lib/libresolv.so.2...done. > Loaded symbols for /lib/libresolv.so.2 > Reading symbols from /usr/lib/libkrb5support.so.0...done. > Loaded symbols for /usr/lib/libkrb5support.so.0 > Reading symbols from /lib/libnss_files.so.2...done. > Loaded symbols for /lib/libnss_files.so.2 > Reading symbols from /lib/libnss_nis.so.2...done. > Loaded symbols for /lib/libnss_nis.so.2 > Reading symbols from /lib/libnsl.so.1...done. > Loaded symbols for /lib/libnsl.so.1 > #0 0x00d4aa0b in _int_malloc () from /usr/lib/lam/libmpi.so.0 > > _______________________________________________ > Developers mailing list > Developers at cactuscode.org > http://www.cactuscode.org/mailman/listinfo/developers > -- Erik Schnetter My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from www.keyserver.net. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://www.cactuscode.org/pipermail/developers/attachments/20071106/22f079aa/attachment.bin From kellerma at aei.mpg.de Tue Nov 6 14:53:21 2007 From: kellerma at aei.mpg.de (Thorsten Kellermann) Date: Tue, 06 Nov 2007 21:53:21 +0100 Subject: [Developers] error message In-Reply-To: <35DDBF1A-D8E1-4BDB-9EC8-80CE4F0FB3DD@cct.lsu.edu> References: <4730B38B.5060909@aei.mpg.de> <35DDBF1A-D8E1-4BDB-9EC8-80CE4F0FB3DD@cct.lsu.edu> Message-ID: <4730D441.3010401@aei.mpg.de> Erik Schnetter wrote: > On Nov 6, 2007, at 12:33:47, Thorsten Kellermann wrote: > >> Can somebody explain me >> what this debugger message means ? >> >> Thorsten > > Hi Thorsten, > > I think you have multiple issues at the same time: > >> Reading symbols from shared object read from target memory...done. >> Loaded system supplied DSO at 0x406000 >> Core was generated by `../../exe/cactus_Whisky2D_RNSID_new >> GRRNSID_50s_axis_rot_0.67.par'. >> Program terminated with signal 11, Segmentation fault. > > This means that you either have an array/pointer error, or that you > ran out of memory. > Strange this is the only thing, what I make sense to me. Because I changed some lines in Cartoon may, I set a point wron. Thorsten From hinder at gravity.psu.edu Wed Nov 7 00:31:42 2007 From: hinder at gravity.psu.edu (Ian Hinder) Date: Wed, 07 Nov 2007 01:31:42 -0500 Subject: [Developers] Detection of gfortran Message-ID: <47315BCE.1090501@gravity.psu.edu> 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? -- Ian Hinder hinder at gravity.psu.edu http://www.gravity.psu.edu/~hinder From jtao at cct.lsu.edu Wed Nov 7 00:53:12 2007 From: jtao at cct.lsu.edu (Jian Tao) Date: Wed, 07 Nov 2007 00:53:12 -0600 Subject: [Developers] Detection of gfortran In-Reply-To: <47315BCE.1090501@gravity.psu.edu> References: <47315BCE.1090501@gravity.psu.edu> Message-ID: <473160D8.5050409@cct.lsu.edu> Forgot to link -lgfortran ? 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? > From hinder at gravity.psu.edu Wed Nov 7 00:55:28 2007 From: hinder at gravity.psu.edu (Ian Hinder) Date: Wed, 07 Nov 2007 01:55:28 -0500 Subject: [Developers] Detection of gfortran In-Reply-To: <473160D8.5050409@cct.lsu.edu> References: <47315BCE.1090501@gravity.psu.edu> <473160D8.5050409@cct.lsu.edu> Message-ID: <47316160.9080503@gravity.psu.edu> 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 -- Ian Hinder hinder at gravity.psu.edu http://www.gravity.psu.edu/~hinder From jtao at cct.lsu.edu Wed Nov 7 01:01:56 2007 From: jtao at cct.lsu.edu (Jian Tao) Date: Wed, 07 Nov 2007 01:01:56 -0600 Subject: [Developers] Detection of gfortran In-Reply-To: <47316160.9080503@gravity.psu.edu> References: <47315BCE.1090501@gravity.psu.edu> <473160D8.5050409@cct.lsu.edu> <47316160.9080503@gravity.psu.edu> Message-ID: <473162E4.2090207@cct.lsu.edu> 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 > > From jtao at cct.lsu.edu Wed Nov 7 01:34:46 2007 From: jtao at cct.lsu.edu (Jian Tao) Date: Wed, 07 Nov 2007 01:34:46 -0600 Subject: [Developers] Detection of gfortran In-Reply-To: <473162E4.2090207@cct.lsu.edu> References: <47315BCE.1090501@gravity.psu.edu> <473160D8.5050409@cct.lsu.edu> <47316160.9080503@gravity.psu.edu> <473162E4.2090207@cct.lsu.edu> Message-ID: <47316A96.5020007@cct.lsu.edu> libgfortran.a was supposed to be added when ... elif test "`$F90 -dumpversion 2>&1 | grep 'GNU Fortran 95'`" ; ... However if you run the latest version (I am not sure which version starts not outputing "GNU Fortran 95") of gfortran with -dumpversion you will not have that "95". That is why it is now working now. I don't know if anyone have a quick fix for this. We might grep gcc version but that is not a good idea anyway. -------------------------------------------- $ gfortran -dumpversion GNU Fortran (GCC) 4.1.2 20070626 (Red Hat 4.1.2-13) Copyright (C) 2007 Free Software Foundation, Inc. GNU Fortran comes with NO WARRANTY, to the extent permitted by law. You may redistribute copies of GNU Fortran under the terms of the GNU General Public License. For more information about these matters, see the file named COPYING Regards, Jian Jian Tao wrote: > 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 >> > > _______________________________________________ > Developers mailing list > Developers at cactuscode.org > http://www.cactuscode.org/mailman/listinfo/developers > From jtao at cct.lsu.edu Wed Nov 7 02:05:06 2007 From: jtao at cct.lsu.edu (Jian Tao) Date: Wed, 07 Nov 2007 02:05:06 -0600 Subject: [Developers] Detection of gfortran In-Reply-To: <47316B90.4090109@gravity.psu.edu> References: <47315BCE.1090501@gravity.psu.edu> <473160D8.5050409@cct.lsu.edu> <47316160.9080503@gravity.psu.edu> <473162E4.2090207@cct.lsu.edu> <47316A96.5020007@cct.lsu.edu> <47316B90.4090109@gravity.psu.edu> Message-ID: <473171B2.4000001@cct.lsu.edu> Ian Hinder wrote: > Jian Tao wrote: >>>>>> (2) Why was there no error message that the compiler was not >>>>>> recognized >>>>>> correctly? gfortran is missing from configure.in and configure. It is never tested during the configuration stage. It should be fixed. ------------ if test -z "$F90" ; then AC_CHECK_PROGS(F90, f90 pgf90 xlf90 ifort) fi ... if test -z "$F90" ; then for ac_prog in f90 pgf90 xlf90 ifort do ------------ From jtao at cct.lsu.edu Wed Nov 7 02:47:13 2007 From: jtao at cct.lsu.edu (Jian Tao) Date: Wed, 07 Nov 2007 02:47:13 -0600 Subject: [Developers] Detection of gfortran In-Reply-To: <473171B2.4000001@cct.lsu.edu> References: <47315BCE.1090501@gravity.psu.edu> <473160D8.5050409@cct.lsu.edu> <47316160.9080503@gravity.psu.edu> <473162E4.2090207@cct.lsu.edu> <47316A96.5020007@cct.lsu.edu> <47316B90.4090109@gravity.psu.edu> <473171B2.4000001@cct.lsu.edu> Message-ID: <47317B91.5010200@cct.lsu.edu> Sorry, that is for automatic compiler detection not for error checking. Regards, Jian Jian Tao wrote: > gfortran is missing from configure.in and configure. It is never > tested during the configuration stage. It should be fixed. > > ------------ > if test -z "$F90" ; then > AC_CHECK_PROGS(F90, f90 pgf90 xlf90 ifort) > fi > ... > if test -z "$F90" ; then > for ac_prog in f90 pgf90 xlf90 ifort > do > ------------ > _______________________________________________ > Developers mailing list > Developers at cactuscode.org > http://www.cactuscode.org/mailman/listinfo/developers >