<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 08/14/2017 10:19 AM, Jeff Layton
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:158a0a4f-450a-be1e-5512-e96974075f5d@att.net">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div class="moz-cite-prefix">On 08/14/2017 03:51 AM, Ralf Gommers
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABL7CQiMYsUJo8Yso6YjKsToTBUi5VhdFhqqVocGvHfmP7Mr0g@mail.gmail.com">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote"><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"> <br>
<br>
<br>
I'm definitely at a lose here. I have no idea how to
make F2PY work with the PGI compilers. I'm beginning
to think F2PY is completely borked unless you use the
defaults (gcc).<br>
</div>
</blockquote>
<div><br>
</div>
<div>That's not the case. Here is an example when using
the Intel Fortran compiler together with either MSVC or
Intel C compilers: <a
href="https://software.intel.com/en-us/articles/building-numpyscipy-with-intel-mkl-and-intel-fortran-on-windows"
moz-do-not-send="true">https://software.intel.com/en-us/articles/building-numpyscipy-with-intel-mkl-and-intel-fortran-on-windows</a><br>
<br>
</div>
<div>I notice there that in all cases the C compiler is
explicitly specified. Did you also try ``<span
class="gmail-">--compiler=gcc --fcompiler=pg</span>``?<br>
<br>
</div>
<div>Also, I'm not sure how often this is done with f2py
directly; I've only ever used the --fcompiler flag via
``python setup.py config --fcompiler=..<etc>``,
invoking f2py under the hood. It could be that doing
this directly is indeed broken (or was never supported
in the first place).<br>
<br>
</div>
<div>Ralf<br>
<br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Point taken. I don't use Windows too much and I don't use the
Intel compiler any more (it's not free for non-commercial use :)
).<br>
<br>
I tried using "--compiler=gcc --fcompiler=pg" and I get the same
answer at the very end.<br>
<br>
<br>
running build_ext<br>
error: don't know how to compile C/C++ code on platform 'posix'
with 'gcc' compiler<br>
<br>
<br>
Good point about f2py. I'm using the Anaconda distribution of f2py
and that may have limitations with respect to the PGI compiler. I
may download the f2py source and build it to include PGI support.
Maybe that will fix the problem.<br>
<br>
Thanks!<br>
<br>
Jeff<br>
<br>
<br>
</blockquote>
<p><br>
</p>
</body>
</html>