Hi Ben, On 12-01-16 04:51, Ben Roberts wrote:
> I’m still trying to get my head around how I can use the Intel compilers with > MPI. Maybe this isn’t an issue now that I’m at EB 2.6.0. > > In brief, it seems that whatever I do the compilers being used are mpicc and > mpif90. I understand that this uses the GCC compilers even though the Intel > toolchain has been requested. As Jack already pointed out, we set the compiler that mpicxx and friends should use. > The program I’m trying to build (CPMD), unfortunately, incorporates the value > of the CC environment variable and so on into a Makefile. This means that if > these environment variables are reset between the configure and make > operations, the changes aren’t reflected in the build step. That's annoying but unfortunately too common (See all the patches in the tree). Patching the makefiles is the only way... > This brings me to the second problem. I’m trying to find all the places where > CC and so on are explicitly set, so they can be commented out if need be > (thus forcing the use of the environment value of CC). But the build > directory is deleted at the end of the build. I’ve tried the > --cleanup-builddir option, and this doesn’t prevent the deletion, and > --cleanup-builddir=false gives me a rather terse warning about how > --cleanup-builddir doesn’t take options. > > How can I keep the build dir for investigative purposes? “cleanupoldbuild” in > the easyconfig doesn’t seem quite right as this seems related to previous > builds, but maybe I’m missing something here. You need --disable-cleanup-builddir. Ward -- dr. ir. Ward Poelmans High Performance Computing infrastructure unit Ghent University Krijgslaan 281 S9 B-9000 Gent Belgium Tel: +32 9 264 4817 http://www.ugent.be/hpc
