Hello Ryan et al., Thank you for your quick reply.
> If you want to build anything from source on macOS, use clang unless there is > an extremely good reason to use gcc. When you say clang, do you recommend using Apple’s clang or clang from MacPorts? One extremely good reason to use gcc is the ability to have a Fortran compiler. I need an MPICH distribution with Fortran compiler wrappers and Fortran modules. > You said in the subject line that you're using gcc 13.2.0 but that's not > confirmed by the log. When I researched this error recently, I found that > this bug was fixed in gcc 11.1 which makes me think you are actually trying > to use a gcc version older than that. See > https://trac.macports.org/ticket/69632 I set gcc to point to mp-gcc13 with a MacPorts command: sudo port select --set gcc mp-gcc13 In my Perl script I ensure FC, CC and CXX environment variables point to compilers in /opt/local/bin/{gcc,g++,gfortran}. Is there any other way to verify that I’m using the right version of GNU compilers? > In your script the flag -I /opt/local/include/unistring/cdefs.h will not help > anything because /opt/local/include/unistring/cdefs.h is not a directory that > contains headers. This was my futile attempt to ‘include’ the correct ‘cdefs.h’ header file, that was causing problems. Thank you for your help and have a great day ahead! — Best wishes, Maxim Maxim Abalenkov \\ maxim.abalen...@gmail.com +44 7 486 486 505 \\ www.maxim.abalenkov.uk > On 13 May 2024, at 14:51, Ryan Schmidt <ryandes...@macports.org> wrote: > > On May 13, 2024, at 05:36, Maxim Abalenkov wrote: >> >> Dear all, >> >> How are you? I hope all is well with you. I need help please. I’m struggling >> to compile MPICH v4.2.1 (from source code) with the GNU toolchain v13.2.0 @ >> macOS Sonoma v14.4.1. Please see my configuration and installation Perl >> script attached. I also attach a full log of the compilation errors. I >> recently installed GNU toolchain via MacPorts. When the script proceeds to >> compilation, it crashes with the following error messages: >> >> Compiling MPICH... >> In file included from >> /Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk/usr/include/sys/_types.h:32, >> from >> /Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk/usr/include/_types.h:27, >> from >> /Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk/usr/include/pthread.h:55, >> from ../../../modules/yaksa/src/util/yaksu_atomics.c:6: >> /Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk/usr/include/sys/cdefs.h:554:30: >> error: missing ')' after "__has_attribute" >> 554 | #if __has_cpp_attribute(clang::unsafe_buffer_usage) >> | ^ >> /Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk/usr/include/sys/cdefs.h:554:31: >> error: ':' without preceding '?' >> 554 | #if __has_cpp_attribute(clang::unsafe_buffer_usage) >> >> I suspect that Apple compilers’ header files are picked up erroneously. Is >> this normal for GNU toolchain to rely on Apple SDK’s header files? I’m new >> to Apple CPUs. Would you please educate me, what is the suggested way of >> installing software on Apple M? processors from source? Or should I just >> save the pain and install my code using Apple’s native toolchain? Thank you >> for your help and have a productive week ahead! > > If you want to use mpich, the easiest solution is to use MacPorts to install > it. > > If you want to build anything from source on macOS, use clang unless there is > an extremely good reason to use gcc. > > You said in the subject line that you're using gcc 13.2.0 but that's not > confirmed by the log. When I researched this error recently, I found that > this bug was fixed in gcc 11.1 which makes me think you are actually trying > to use a gcc version older than that. See > https://trac.macports.org/ticket/69632 > > In your script the flag -I /opt/local/include/unistring/cdefs.h will not help > anything because /opt/local/include/unistring/cdefs.h is not a directory that > contains headers.
