[Users] Issues getting Einstein Toolkit built on Scientific Linux 6
Joe Hellmers
jhellmer at rohan.sdsu.edu
Mon Dec 10 15:52:37 CST 2012
After adding the optionlist for sl6.cfg, I'm not getting the same error, but I am getting
sol_elliptic_sin_zec.C:56:31: error: gsl/gsl_sf_bessel.h: No such file or directory
make[5]: *** [sol_elliptic_sin_zec.o] Error 1
make[4]: *** [install] Error 2
make[3]: *** [Source/Non_class_members/PDE] Error 2
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [cpp] Error 2
CST error 1:
-> Configuration script for thorn LORENE returned exit code 1
(no error message)
and then at the end
------------------------------------------------------
There were 2 errors during execution of the CST
These must be corrected before compilation can proceed
------------------------------------------------------
------------------------------------------------------
Warnings were generated during execution of the CST
------------------------------------------------------
CST error 1:
-> Configuration script for thorn LORENE returned exit code 1
(no error message)
CST error 2:
-> Configuration script for thorn HWLOC returned exit code 1
(no error message)
------------------------------------------------------
make[1]: *** [/home/hellmersjl/EinsteinToolkit/Cactus/configs/sim/config-data/make.thornlist] Error 1
make: *** [sim] Error 2
On Dec 10, 2012, at 12:46 AM, Eloisa Bentivegna wrote:
> On Dec 10, 2012, at 2:14 AM, Joe Hellmers wrote:
>
>> I'm brand new to the Einstein Toolkit and to Cactus, so be gentle with me.
>>
>> I'm getting some messages similar to
>>
>> "CST error 1:
>> -> Configuration script for thorn BLAS returned exit code 1
>> Error message: 'Building BLAS requires a Fortran compiler, but there is none configured:
>> F77='none'.
>> Aborting.
>>
>>
>> I looked to the sl6.cfg file and both F77 and F90 are set to gfortran, and gfortran is installed
>>
>> Thanks.
>>
>> Is there another configuration file somewhere that needs to be updated?
>
> Hi Joe,
>
> can you post the exact command that you're using to build your code? If you're building with simfactory, you need to give it some information regarding which optionlist you want to use. The most straightforward way to do this is by adding an
>
> --optionlist=sl6.cfg
>
> to your build command. Otherwise you can teach it to automatically recognize your machine by creating a yourmachine.ini file under simfactory/mdb/machines, and setting the default optionlist in there.
>
> Does this help?
>
> Eloisa
More information about the Users
mailing list