Hey Luca,

The easiest workaround to build your library might be to replace the Lorene.tar.gz with your own Lorene source directory. If this works you could probably introduce the arguments into the Lorene.sh script to do this automatically and make it more permanent and less hackish. If you really want to see the local_settings, you could add a line after

     cat > local_settings <<EOF

CXX = ${CXX} CXXFLAGS = ${CXXFLAGS} ${CPP_OPENMP_FLAGS} CXXFLAGS_G = ${CXXFLAGS} F77 = ${F77} F77FLAGS = ${F77FLAGS} ${FIXEDF77FLAGS} F77FLAGS_G = ${F77FLAGS} ${FIXEDF77FLAGS} INC = -I$(HOME_LORENE)/C++/Include -I$(HOME_LORENE)/C++/Include_extra $(addprefix -I,${GSL_INC_DIRS}) RANLIB = ${RANLIB} # We don't need dependencies since we always build from scratch #MAKEDEPEND = ${CXX_DEPEND} $(INC) $< ${CXX_DEPEND_OUT} && mv $@ $(df).d MAKEDEPEND = : > $(df).d DEPDIR = .deps FFT_DIR = FFT991 LIB_CXX = ${LIBS} LIB_LAPACK = ${LAPACK_LIBS} ${BLAS_LIBS} LIB_PGPLOT = LIB_GSL = ${GSL_LIBS} DONTBUILDDEBUGLIB = yes EOF

such as :

copy local_settings ~/local_settings_autogenerated

and then you should be able to read it at your leisure.

Hope that helps.

Aaryn Tonita

On Tue, Nov 01, 2011 at 10:56:48PM +0900, Luca Baiotti wrote:

However, I need to compile some non-standard code into Lorene, so I cannot use ExternalLibraries/LORENE. (Or can I?)

LORENE already applies patches before it is build. Could you put your changes into such a patch and apply it before building as well? You wouldn't have to commit it of course, and it would be probably the cleanest way for you.

(Look at LORENE.sh:95 and the *.patch files in dist/)

Frank

Luca

There is a "rm -rf" statement near the end of the script that deletes Lorene's build directory ("cleaning up"). If you comment this out, you'll see the generated local_settings file in the directory Cactus/configs/.../scratch/build/LORENE.

-erik

On Tue, Nov 1, 2011 at 9:56 AM, Luca Baiotti baiotti@ile.osaka-u.ac.jp wrote:

Hello.

Lorene is notoriously difficult to build (I mean, it is difficult to choose the appropriate local_settings to build it) and the thorn ExternalLibraries/LORENE is very helpful.

However, I need to compile some non-standard code into Lorene, so I cannot use ExternalLibraries/LORENE. (Or can I?)

So I need to compile Lorene by myself but I would like to use the settings determined by ExternalLibraries/LORENE. In ExternalLibraries/LORENE/LORENE.sh I found the lines:

cat > local_settings <<EOF CXX = ${CXX} CXXFLAGS = ${CXXFLAGS} ${CPP_OPENMP_FLAGS} CXXFLAGS_G = ${CXXFLAGS} F77 = ${F77} F77FLAGS = ${F77FLAGS} ${FIXEDF77FLAGS} F77FLAGS_G = ${F77FLAGS} ${FIXEDF77FLAGS} INC = -I$(HOME_LORENE)/C++/Include -I$(HOME_LORENE)/C++/Include_extra $(addprefix -I,${GSL_INC_DIRS}) RANLIB = ${RANLIB} # We don't need dependencies since we always build from scratch #MAKEDEPEND = ${CXX_DEPEND} $(INC) $< ${CXX_DEPEND_OUT} && mv $@ $(df).d MAKEDEPEND = : > $(df).d DEPDIR = .deps FFT_DIR = FFT991 LIB_CXX = ${LIBS} LIB_LAPACK = ${LAPACK_LIBS} ${BLAS_LIBS} LIB_PGPLOT = LIB_GSL = ${GSL_LIBS} DONTBUILDDEBUGLIB = yes EOF

but I could not make out directly the values of all the parameters. Is there a way to print out the local_settings file produced and used by ExternalLibraries/LORENE? Any help is welcome.

Cheers,

Luca _______________________________________________ Users mailing list Users@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/users