fftw-3 @3.3.8_1+gfortran: Uses wrong SDK

[murrayE]

From config.log:

configure:4448: /usr/bin/clang -v >&5
Apple clang version 12.0.0 (clang-1200.0.32.29)
Target: x86_64-apple-darwin20.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
configure:4459: $? = 0
configure:4448: /usr/bin/clang -V >&5
clang: error: argument to '-V' is missing (expected 1 value)
clang: error: no input files
configure:4459: $? = 1
configure:4448: /usr/bin/clang -qversion >&5
clang: error: unknown argument '-qversion'; did you mean '--version'?
clang: error: no input files
configure:4459: $? = 1
configure:4479: checking whether the C compiler works
configure:4501: /usr/bin/clang -pipe -O3 -fno-common -fomit-frame-pointer -fstrict-aliasing -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.0.sdk -arch x86_64 -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.0.sdk -L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX11.0.sdk -arch x86_64 conftest.c  >&5
ld: library not found for -lSystem
clang: error: linker command failed with exit code 1 (use -v to see invocation)
configure:4505: $? = 1
configure:4543: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "fftw"
| #define PACKAGE_TARNAME "fftw"
| #define PACKAGE_VERSION "3.3.8"
| #define PACKAGE_STRING "fftw 3.3.8"
| #define PACKAGE_BUGREPORT "fftw@fftw.org"
| #define PACKAGE_URL ""
| #define PACKAGE "fftw"
| #define VERSION "3.3.8"
| #define FFTW_ENABLE_ALLOCA 1
| #define HAVE_SSE2 1
| #define HAVE_AVX 1
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| 
|   ;
|   return 0;
| }
configure:4548: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_fftw-3/fftw-3/work/fftw-3.3.8':
configure:4550: error: C compiler cannot create executables

[murrayE]

config.log

[ryandesign (Ryan Carsten Schmidt)]

You did not mention here what version of Xcode you use, but you mentioned elsewhere (in #61321) that you use Xcode 12.4 and the compiler version shown above (clang-1200.0.32.29) confirms that.

The log above shows that it is trying to use MacOSX11.0.sdk, which does not exist in Xcode 12.4.

Please attach the main.log so that we can see whether MacPorts base is specifying the wrong SDK to the build (if so, that would seem to be #61866 though it was supposed to have been fixed already) or whether the build is finding the wrong SDK on its own.

[murrayE]

main.log

[jmroot (Joshua Root)]

More or less the same as #61866, apparently some update deleted most of the contents of MacOSX11.0.sdk but left the directory, which MacPorts assumes must be usable if it exists.

[murrayE]

In /Library/Developer/CommandLineTools/SDKs I find MacOSX10.14.sdk, MacOSX10.15.sdk, MacOSX11.0.sdk, and MacOSX11.1.sdk. Also MacOSX.sdk, which is an alias for MacOSX11.1.sdk.

Whereas MacOSX11.1.sdk consists of some 42,000 items taking 312 MB on disk, MacOSX11.0.sdk consists of only 382 items taking 3.4 MB on disk.

The other two, MacOSX10.14.sdkand MacOSX10.15.sdk are similar in number of files and size to MacOSX11.1.sdk.

Is it totally safe to delete the entire MacOSX11.0.sdk directory?

Should I also delete the older two, too?

[jmroot (Joshua Root)]

Yes, it's a good idea to delete the MacOSX11.0.sdk since it's broken due to missing most of its files anyway. You can delete the SDKs for the older OS versions if you don't want to use them for anything, but leaving them isn't a problem.