Can you send at least your config.log file?  It would be good to know why the 
"STDC" test is reporting that this setup does not have STDC headers when it 
actually does.


> On Apr 23, 2019, at 8:14 PM, John R. Cary <c...@txcorp.com> wrote:
> 
> It appears that the problem is with AC_HEADER_STDC, which is reporting
> that this setup does not have stdc headers when in fact it does.
> 
> Overriding with
> 
>  CFLAGS='-fvisibility=default -mmacosx-version-min=10.10 
> -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include
>  -fPIC -pipe -DSTDC_HEADERS -DOPAL_STDC_HEADERS'
> 
> in particular, the last two defines, fixes this.
> 
> .................John
> 
> 
> 
> On 4/23/2019 4:59 PM, Jeff Squyres (jsquyres) wrote:
>> The version of LLVM that I have installed on my Mac 10.14.4 is:
>> 
>> $ where clang
>> /usr/bin/clang
>> $ clang --version
>> Apple LLVM version 10.0.1 (clang-1001.0.46.4)
>> Target: x86_64-apple-darwin18.5.0
>> Thread model: posix
>> InstalledDir: 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>> 
>> I don't know how that compares to upstream clang v7.x...?
>> 
>> More below.
>> 
>> 
>> 
>>> On Apr 23, 2019, at 6:26 PM, John R. Cary via users 
>>> <users@lists.open-mpi.org> wrote:
>>> 
>>> The failure is
>>> 
>>> In file included from 
>>> /Users/cary/projects/ulixesall-llvm/builds/openmpi-4.0.1/nodl/../ompi/datatype/ompi_datatype_external.c:29:
>>> In file included from 
>>> /Users/cary/projects/ulixesall-llvm/builds/openmpi-4.0.1/nodl/../ompi/communicator/communicator.h:38:
>>> In file included from 
>>> /Users/cary/projects/ulixesall-llvm/builds/openmpi-4.0.1/nodl/../ompi/errhandler/errhandler.h:33:
>>> ../../ompi/include/mpi.h:397:9: error: unknown type name 'ptrdiff_t'
>>> typedef OMPI_MPI_AINT_TYPE MPI_Aint;
>>>         ^
>>> ../../opal/include/opal_config.h:1911:28: note: expanded from macro 
>>> 'OMPI_MPI_AINT_TYPE'
>>> #define OMPI_MPI_AINT_TYPE ptrdiff_t
>>> 
>>> 
>>> Is there a known fix for this?
>>> 
>>> Thx...John Cary
>>> 
>>> 
>>> More info:
>>> 
>>> Configured with
>>> 
>> A few notes on your configure line:
>> 
>>> '/Users/cary/projects/ulixesall-llvm/builds/openmpi-4.0.1/nodl/../configure'
>>>  \
>>> --prefix=/Volumes/GordianStorage/opt/contrib-llvm7_appleclang/openmpi-4.0.1-nodl
>>>  \
>>> CC='/Volumes/GordianStorage/opt/clang+llvm-7.0.0-x86_64-apple-darwin/bin/clang'
>>>  \
>>> CXX='/Volumes/GordianStorage/opt/clang+llvm-7.0.0-x86_64-apple-darwin/bin/clang++'
>>>  \
>> The MPI C++ bindings are no longer built by default, and you're not enabling 
>> them (via --enable-mpi-cxx), so you don't need to specify CXX or CXXFLAGS 
>> here.
>> 
>>>   FC='/opt/homebrew/bin/gfortran-6' \
>>>   F77='/opt/homebrew/bin/gfortran-6' \
>> F77 is ignored these days; FC is the only one that matters.
>> 
>>>   CFLAGS='-fvisibility=default -mmacosx-version-min=10.10 
>>> -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include
>>>  -fPIC -pipe -DSTDC_HEADERS' \
>> Do you need all these CFLAGS?  E.g., does clang not -I that directory by 
>> default (I don't actually know if it is necessary or not)?  What does 
>> -DSTDC_HEADERS do?
>> 
>>>   CXXFLAGS='-std=c++11 -stdlib=libc++ -fvisibility=default 
>>> -mmacosx-version-min=10.10 
>>> -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include
>>>  -fPIC -pipe' \
>>>   FCFLAGS='-fPIC -pipe' \
>>>   --enable-static \
>>>   --with-pic \
>>>   --disable-dlopen \
>>>   --enable-mpirun-prefix-by-default
>> I don't have that version of clang, but I installed gfortran 6.3.0 via 
>> homebrew and configured with:
>> 
>> ./configure --prefix=/Users/jsquyres/bogus CC=clang FC=gfortran 
>> 'CFLAGS=-fvisibility=default -mmacosx-version-min=10.10 
>> -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include
>>  -fPIC -pipe -DSTDC_HEADERS' 'FCFLAGS=-fPIC -pipe' --enable-static 
>> --with-pic --disable-dlopen --enable-mpirun-prefix-by-default
>> 
>> And Open MPI v4.0.1 build ok for me...?
>> 
>> Can you send all the information listed here:
>> 
>>     https://www.open-mpi.org/community/help/
>> 
> 


-- 
Jeff Squyres
jsquy...@cisco.com

_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users

Reply via email to