Well, jtull over at PGI seemed to have the "magic sauce":
http://www.pgroup.com/userforum/viewtopic.php?p=21105#21105
Namely, I think it's the siterc file. I'm not sure which of the adaptations
fixes the issue yet, though.
On Mon, Nov 28, 2016 at 3:11 PM, Jeff Hammond
wrote:
> attached config.
Note that Matt was quite correct, things seem to go fine with the
configure tests up until it gets to the libevent portion.
I include what appears to be the first major error block from
config.log below. The first error is triggered by this:
/* This SDK is designed to work with clang and specifi
attached config.log that contains the details of the following failures is
the best way to make forward-progress here. that none of the system
headers are detected suggests a rather serious compiler problem that may
not have anything to do with headers.
checking for sys/types.h... no
checking for
You could try an explicit
$ export CFLAGS="-I/usr/include"
prior to running ./configure and see if that has any effect.
If it still throws the error, you can examine the full compile line
that make prints when it tries to compile the source file to see
whether the explicit include made it. If i
Hmm. Well, I definitely have /usr/include/stdint.h as I previously was
trying work with clang as compiler stack. And as near as I can tell, Open
MPI's configure is seeing /usr/include as oldincludedir, but maybe that's
not how it finds it?
If I check my configure output:
=
I think PGI uses installed GCC components for some parts of standard C
(at least for some things on Linux, it does; and I imagine it is
similar for Mac). If you look at the post at
http://www.pgroup.com/userforum/viewtopic.php?t=5147&sid=17f3afa2cd0eec05b0f4e54a60f50479
The problem seems to have
The following is the code that fails. The comments indicate the likely
source of the error.
Please see
http://www.pgroup.com/userforum/viewtopic.php?t=5147&sid=17f3afa2cd0eec05b0f4e54a60f50479
and other entries on https://www.google.com/search?q=pgi+stdint.h.
You may want to debug libevent by it
All,
I recently tried building Open MPI 2.0.1 with the new Community Edition of
PGI on macOS. My first mistake was I was configuring with a configure line
I'd cribbed from Linux that had -fPIC. Apparently -fPIC was removed from
the macOS build. Okay, I can remove that and I configured with:
./con