I have tried again w/ flags nearly identical to Larry's:
$ [path_to]/configure --with-contrib-vt-flags=--with-platform=linux
--with-sge \
CC="pathcc-3.2 -m64"CFLAGS="-g -O3 -march=anyx86" \
CXX="pathCC-3.2 -m64"CXXFLAGS="-g -O1 -march=anyx86" \
FC="pathf90-3.2 -m64"FCFLAGS
I have built both 1.4.3rc1 and 1.5rc5 using the 3.2 PathScale compilers.
I did not encounter the problem Larry reported, but there are (at least)
2 differences between my build and Larry's
1) I didn't pass and explicit {C,CXX,F,FC}FLAGS
2) My pathcc install is using the gcc4 toolchain, not gcc3
You can always disable vampir trace in OMPI:
./configure --enable-contrib-no-build=vt
That will avoid building this optional component and therefore you won't run
into this compiler issue.
On Aug 27, 2010, at 5:18 PM, Larry Baker wrote:
> The PathScale 3.2 C++ compiler segment faults for
Among the tests I conducted but did not report was a successful build of
1.5rc5 with the PathScale "3.2.99" compilers.
$ pathcc --version
PathScale(TM) Compiler Suite: Version 3.2.99
Built on: 2009-08-21 13:23:57 -0500
Thread model: posix
GNU gcc version 4.2.0 (PathScale 3.2.99 driver)
Copyright
