[Users] questions about compilation
林家暉
r06222015 at ntu.edu.tw
Thu Dec 14 01:49:15 CST 2017
Dear Roland,
Thanks for your kindly reply !
Sorry for bothering you for several times.
I tried your suggestion and solved the both error of -ljpeg and dlopen.
And it was showed that:
Done creating cactus_sim.
All done !
However the compilation is not finished.The process of building utilities for sim started. And another error occurred, as showed in the screenshot. It seems to be similar to the problem in the link:
http://lists.einsteintoolkit.org/pipermail/trac/2011-October/002449.html
But I did not find a solution to this error.Is there some possible solution?
By the way, I commented some module loading in the edison.ini since some of them cannot successfully loaded (maybe because the version of those modules are outdated , and some module even not appear in the module list of edison) . As showed in another screenshot. I am afraid that this caused the occurrence of some error.
Best regards,
Chia Hui Lin
________________________________________
從: Roland Haas [roland.haas at physics.gatech.edu]
寄件日期: 2017年11月28日 上午 03:28
至: 林家暉
副本: users at einsteintoolkit.org
主旨: Re: [Users] questions about compilation
Hello Chia Hui Lin,
hmm. I am not sure about the -ljpeg since ExternalLibraries/libjpeg
should provide this.
You are also receiving a link time warning about using dlopen in a
statically linked application. While not directly related to the jpeg
library issue a possible workaround is force dynamic linking (not the
default one edison) by setting:
export CRAYPE_LINK_TYPE=dynamic
export CRAY_ADD_RPATH=yes
either as part of the envsetup lines in the file
simfactory/mdb/machine/edison.ini or on your command line (if eg not
using simfactory).
Yours,
Roland
> Dear Roland,
> Thanks for your kindly help and sorry for replying such late.
> It indeed solved the error by using the second method you suggested.
> However another error occurred , the attached file is the screenshot of the error message.
> It seems the code cannot find the library of jepg , but I think it is not missing since I found some versions of it by using the command :ldconfig -p | grep jepg (showed in the screenshot).
> Although I tried several compilers including intel compiler version 16, it did not work.
> What kind of the problem is it and is there some possible solutions ?
> Thank you .
> Best regards,
> Chia Hui Lin
> ________________________________________
> 從: Roland Haas [roland.haas at physics.gatech.edu]
> 寄件日期: 2017年11月21日 上午 12:42
> 至: 林家暉
> 副本: users at einsteintoolkit.org
> 主旨: Re: [Users] questions about compilation
>
> Hello Chia Hui Lin,
>
> looking at your output (internal compiler failure when compiling
> bbox.cc) this seems to be an instance of this bug:
>
> https://trac.einsteintoolkit.org/ticket/2021
>
> there seem to be two way around this:
>
> 1. change the file edison.ini to load an older Intel compiler (version
> 16)
> 2. edit the file repos/carpet/CarpetLib/src/bbox.cc and add at the
> beginning:
>
> #if __INTEL_COMPILER >= 1700
> #pragma GCC optimization_level 1
> #endif
>
> which reduces the optimization level and avoids the problem.
>
> Yours,
> Roland
>
> > Dear sir/madam,
> > I am a master student of physics department ,National Taiwan University, and a beginner of Einstein toolkit.
> > I started with my laptop and everything worked fine. While I turning to super cluster called Edison ,NERSC, some errors came up during compilation(that is, after I type the command:$ ./simfactory/bin/sim build ).
> > 1.The attached file is the screenshot of the error message. It seems the error is caused by compiler. However the same error appeared after shifting the intel compiler to cray compiler or gnu compiler.How can I solve the error?
> >
> > 2.The machine definition file of Edison(edison.ini) is last tested in May,2015, so I am afraid that some information of the machine is outdated . Is this related to the previous problem(1.)? How can I update this file ?
> >
> > Thanks for your help.
> > Best regards,
> > Chia Hui Lin
> >
> >
>
>
>
> --
> My email is as private as my paper mail. I therefore support encrypting
> and signing email messages. Get my PGP key from http://pgp.mit.edu .
--
My email is as private as my paper mail. I therefore support encrypting
and signing email messages. Get my PGP key from http://pgp.mit.edu .
-------------- next part --------------
A non-text attachment was scrubbed...
Name: error_message.png
Type: image/png
Size: 772217 bytes
Desc: error_message.png
Url : http://lists.einsteintoolkit.org/pipermail/users/attachments/20171214/c40fa0e3/attachment-0002.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: edison_module.png
Type: image/png
Size: 126937 bytes
Desc: edison_module.png
Url : http://lists.einsteintoolkit.org/pipermail/users/attachments/20171214/c40fa0e3/attachment-0003.png
More information about the Users
mailing list