<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Nov 4, 2014, at 5:20 PM, Richard Mills <<a href="mailto:richardtmills@gmail.com" class="">richardtmills@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I
noticed that you are using the wrong compiler wrappers. Instead of 'mpicc', 'mpif90', and 'mpicxx' (which will invoke GNU compilers), you probably want 'mpiicc', 'mpiifort', and 'mpiicpc' (invoke the Intel compilers).</span></div>
</blockquote>
</div>
<br class="">
<div class="">May I remark that that’s a silly setup? It’s far more convenient to have the mpi compiler script to have the same name always, regardless of what compiler and MPI you have loaded.</div>
<div class=""><br class="">
</div>
<div class="">I understand that you’re already using the software modules system, so there is no reason not to do it that way: the search path is dynamically set so you get the right script automatically.</div>
<div class=""><br class="">
</div>
<div class="">Btw, if you haven’t replaced the environment modules by lmod (developed at TACC and backwards compatible but far better) you’re behind the times….</div>
<div class=""><br class="">
</div>
<div class="">Victor.</div>
<div class=""><br class="">
</div>
</body>
</html>