Opened 8 years ago
Last modified 8 years ago
#10314 new Bugs
Update 59fd3b6 on May 17 to cray.jam breaks cray build
| Reported by: | Owned by: | ||
|---|---|---|---|
| Milestone: | To Be Determined | Component: | Building Boost |
| Version: | Boost 1.56.0 | Severity: | Regression |
| Keywords: | Cc: | kbelco@… |
Description
Download the 1.56 boost beta.
do: ./bootstrap.sh
./b2 --with-serialization --with-system --with-filesystem --with-date_time --with-program_options --with-test -d2 toolset=cray stage
Get lots of errors like ...
CC -c -O2 -march=bdver1 -mfpmath=sse -mfma4 -mavx -funroll-all-loops -mprefer-avx128 -fprefetch-loop-arrays --param prefetch-latency=300 -minline-all-stringops -ffast-math -fno-finite-math-only -dynamic -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DDATE_TIME_INLINE -DNDEBUG -I"." -o "bin.v2/libs/date_time/build/cray/release/threading-multi/gregorian/greg_month.o" "libs/date_time/src/gregorian/greg_month.cpp"
CC-2115 crayc++: ERROR in command line
"-march=bdver1" is an invalid command-line option.
CC-2115 crayc++: ERROR in command line
"-mfpmath=sse" is an invalid command-line option.
CC-2115 crayc++: ERROR in command line
"-mfma4" is an invalid command-line option.
CC-2115 crayc++: ERROR in command line
"-mavx" is an invalid command-line option.
CC-2115 crayc++: ERROR in command line
"-mprefer-avx128" is an invalid command-line option.
CC-2115 crayc++: ERROR in command line
"--param" is an invalid command-line option.
CC-2115 crayc++: ERROR in command line
"-minline-all-stringops" is an invalid command-line option.
...failed cray.compile.c++ bin.v2/libs/date_time/build/cray/release/threading-multi/gregorian/greg_month.o... cray.compile.c++ bin.v2/libs/date_time/build/cray/release/threading-multi/gregorian/greg_weekday.o
Not a Boost developer. Just a user that builds boost on cray systems. Looks to me like you have PrgEnv-cray loaded, but you b2 generating gcc specific options? Do you have the same PrgEnv/compiler modules loaded at the time you bootstraped vs when you executed b2?
I build boost with all three compilers, but to keep things "clean" I wipe out b2 and re-bootstrap between each build with a particular compiler family.