Chris Worley wrote:
> Some of those changes for icc don't make sense.  Setting "CC" to "icc
> -i-dynamic" looks for an executable file name of the entire string...
> causing:

Are you pulling that out of config.log or just assuming that's
happening? We build and test with those Intel compiler settings all the
time, and from what I see - what you describe should not be the problem.
Without the config.log, I cannot tell exactly what might be the problem.
You could try building statically and see if that works, as it should
not use those flags. You could modify build.sh and remove those flags,
just to see if that works. Those flags were added in that way because we
had run into an issue with the Intel compiler and building with shared
library support at one point.

What version of the Intel compiler are you using? You could also try
building our latest source release of MVAPICH2 0.9.8 with the same
compiler settings - in order to get the config.log file easier if it
also has a problem.
--
Shaun Rowland rowland@cse....
http://www.cse.ohio-state.edu/~rowland/
_______________________________________________
general mailing list
general@list...
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general