I thought the purpose of the platform file was to be equivalent to setting things on the command-line to configure. Still, it has always worked that way for us.
Here's what I'm seeing: (dog@lo1-fe 297%) ./configure --prefix=/usr/projects/hpcsoft/lobo/openmpi/1.6.0-pgi-12.4 --with-platform=./optimized-panasas-pgi ============================================================================ == Configuring Open MPI ============================================================================ *** Startup tests checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking for gcc... /usr/projects/hpcsoft/lobo/pgi/linux86-64/12.4/bin/pgcc checking whether the C compiler works... no configure: error: in `/usr/projects/hpctools/dog/openmpi/openmpi-1.6': configure: error: C compiler cannot create executables See `config.log' for more details The error happens because this particular compiler, pgi-12.4, needs two flags: -lnomp and -lnuma. Thus the reason for the LDFLAGS line in the platform file. If I compile like this: (dog@lo1-fe 297%) ./configure --prefix=/usr/projects/hpcsoft/lobo/openmpi/1.6.0-pgi-12.4 --with-platform=./optimized-panasas-pgi LDFLAGS="-nomp -lnuma" Then the configure proceeds normally. -david -- David Gunter HPC-3: Infrastructure Team Los Alamos National Laboratory On May 23, 2012, at 12:03 PM, Jeff Squyres (jsquyres) wrote: > Can you send some output showing that those flags aren't passed through, like > some output from "make V=1" and or from config.log? > > Offhand, I don't know if we ever formally supported setting env variables > other than enable and with flag variables in the platform files...? > > Sent from my phone. No type good. > > On May 23, 2012, at 12:49 PM, "Gunter, David O" <d...@lanl.gov> wrote: > >> I am trying to set LDFLAGS, CFLAGS, etc, in a platform file but the 1.6 >> release does not seem to pick these up. >> >> Here's the tail end of one of our platform files, for building with the >> latest PGI compilers: >> >> LDFLAGS="-nomp -lnuma" >> CFLAGS="-I/opt/panfs/include" >> CXXFLAGS="-I/opt/panfs/include" >> FCFLAGS="-I/opt/panfs/include" >> FFLAGS="-I/opt/panfs/include" >> CCASFLAGS="-I/opt/panfs/include" >> >> The same platform file will configure the 1.4.5 release just fine but does >> not work with 1.6. If I set these variables in my environment and then run >> configure, it works just fine - as expected. >> >> Has anyone else noticed this behavior? >> >> -david >> -- >> David Gunter >> HPC-3: Infrastructure Team >> Los Alamos National Laboratory >> >> >> >> >> >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/devel > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
