in the present 6.7.1 inclusion of atompaw, there is a test for libxc presence. With my sequential compiler (still xlf 12.1 suse linux 64 bits), the test fails although the libxc is present, because the conftest_cpp.f90 is at the end of the command line, after the -L/path -lxc
for the parallel compiler, for some reason, this doesn't happen: the -lxc is in the LDFLAGS, instead of the LIBS environment variable (which is the only one placed after the source file in atompaw configure).
The order should somehow be forced - the libs should come afterwards of course...
Matthieu
atompaw configure test command line ordering [SOLVED]
Moderators: fgoudreault, mcote
Forum rules
Please have a look at ~abinit/doc/config/build-config.ac in the source package for detailed and up-to-date information about the configuration of Abinit 8 builds.
For a video explanation on how to build Abinit 7.x for Linux, please go to: http://www.youtube.com/watch?v=DppLQ-KQA68.
IMPORTANT: when an answer solves your problem, please check the little green V-like button on its upper-right corner to accept it.
Please have a look at ~abinit/doc/config/build-config.ac in the source package for detailed and up-to-date information about the configuration of Abinit 8 builds.
For a video explanation on how to build Abinit 7.x for Linux, please go to: http://www.youtube.com/watch?v=DppLQ-KQA68.
IMPORTANT: when an answer solves your problem, please check the little green V-like button on its upper-right corner to accept it.
atompaw configure test command line ordering
Matthieu Verstraete
University of Liege, Belgium
University of Liege, Belgium
Re: atompaw configure test command line ordering [SOLVED]
Correction: the culprit is the wrapper for my fc, which systematically puts the source file at the end of the command line, even when it is used as a linker - what a moron.
I propose to change the wrap-fc so it _always_ puts the cpp preprocessed file just after $FC. Simple, and no reason not to do it.
good - this vindicates the atompaw configure script.
Cheers
Matthieu
I propose to change the wrap-fc so it _always_ puts the cpp preprocessed file just after $FC. Simple, and no reason not to do it.
good - this vindicates the atompaw configure script.
Cheers
Matthieu
Matthieu Verstraete
University of Liege, Belgium
University of Liege, Belgium