My experiences building with ICC..
#1 it failed out of the box with
checking for a supported version of gcc... no (13.1.3)
configure: error: please use gcc >= 3.0 or clang >= 2.9
I had to make some hacks in ./configure to support ICC
notclang-13.*)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: ok (${gcc_version})"
>&5
$as_echo "ok (${gcc_version})" >&6; }
;;
notclang-14.*)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: ok (${gcc_version})"
>&5
$as_echo "ok (${gcc_version})" >&6; }
;;
notclang-14.*)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: ok (${gcc_version})"
>&5
$as_echo "ok (${gcc_version})" >&6; }
;;
#2 ICC needs additional libs linked in, but passing them in through LDFLAGS
was not working, as the link_tool_exe_linux wouldn't accept -L or
-Wl,-rpath for -l libs. Had to shoehorn static libs using make LIBS=libX.a
#3 Patrick's patch for missing PTRACE_GETSIGINFO was also applied since
building on SLES10/11
Final build command is
env CXX=/usr/pkgs/icc/13.1.3e/bin/icpc CC=/usr/pkgs/icc/13.1.3e/bin/icc
CFLAGS="-O3 -xHOST" ./configure && make clean && make
LIBS="/usr/pkgs/icc/13.1.3e/lib/intel64/libirc.a" && make install
Will send feedback on how it runs. Best of luck on the release!
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
