I think I have some understanding of what is happening. In version 1.6, the
check for the platform file occurs after some basic compiler testing has
already occured:
(dog@tu-fe1 61%) ./configure --with-platform=non-existant
===
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=./o
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
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"
FCFL
