Re: fftw3 update failed with C compiler cannot create executables

Thanks Hanspeter,

I didn’t run Xcode-select from the command line, but somehow it was set up (maybe selecting the command line tools in Xcode preferences did it).

xcode-select -p originally gave the /Volumes/LaCie Thunderbolt RAID Set 1/… path below (I’ve lost it out of my scroll back so can’t copy it).

I made an alias to the external drive and set Xcode-select using that:

% xcode-select -p
/Users/mbaudais/raid1/Applications/Xcode.app/Contents/Developer

No change in the fink update results.

When I run “sudo configure” in the fftw build directory, I notice that it continues to use the original path for the “LD" and “InstalledDir” variables:

config.log:
…
configure:4443: gcc --version >&5
Apple clang version 11.0.0 (clang-1100.0.33.17)
Target: x86_64-apple-darwin18.7.0
Thread model: posix
InstalledDir: /Volumes/LaCie Thunderbolt RAID Set 1/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
Configured with: --prefix=/Users/mbaudais/raid1/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Users/mbaudais/raid1/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
configure:4454: $? = 0
configure:4443: gcc -v >&5
Configured with: --prefix=/Users/mbaudais/raid1/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Users/mbaudais/raid1/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
...
configure:6247: checking for ld used by gcc
configure:6314: result: /Volumes/LaCie Thunderbolt RAID Set 1/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
configure:6321: checking if the linker (/Volumes/LaCie Thunderbolt RAID Set 1/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld) is GNU ld
configure:6336: result: no
…

Well I spent some time on this going down the rabbit hole(s), things like how apple is using stubs instead of full libraries and that’s why we need the apple linker, etc.  I’ve determined that the only solution for me is to move Xcode back onto my main drive.  That will resolve the issue I’m sure.  I can’t tell if it’s autoconf that’s messing up the path (by not quoting it properly) or what, but autoconf is looking like a nightmare to figure out.

Thanks again!

Mike



> On 2021-Nov-05, at 5:12 AM, Hanspeter Niederstrasser <[email protected]> wrote:
> 
> On 11/4/21 7:04 PM, Baudais Michael wrote:
>> Hi,
>> I tried searching the archives and haven’t found the smoking gun for this.   Some info:
>> OS 10.14 Mojave, fink 0.45.4, Xcode 11.3.1, Command Line Tools up-to-date
>> Doing a “fink update fftw3”, attempts to upgrade to fftw3-3.3.10.
>> configure:4474: checking whether the C compiler works
>> configure:4496: /sw/bin/gcc-fsf-9 -I/Volumes/LaCie Thunderbolt RAID Set 1/Applications/Xcode.app/Contents/Developer/Plat
>> forms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include -I/sw/include -L/sw/lib conftest.c  >&5
>> gcc-fsf-9: error: Thunderbolt: No such file or directory
>> gcc-fsf-9: error: RAID: No such file or directory
>> gcc-fsf-9: error: Set: No such file or directory
>> gcc-fsf-9: error: 1/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/u
>> sr/include: No such file or directory
>> configure:4500: $? = 1
>> configure:4538: result: no
>> configure: failed program was:
>> | /* confdefs.h */
>> | #define PACKAGE_NAME "fftw"
>> | #define PACKAGE_TARNAME "fftw"
>> | #define PACKAGE_VERSION "3.3.10"
>> | #define PACKAGE_STRING "fftw 3.3.10"
>> | #define PACKAGE_BUGREPORT "[email protected]"
>> | #define PACKAGE_URL ""
>> | #define PACKAGE "fftw"
>> | #define VERSION "3.3.10"
>> | #define FFTW_ENABLE_ALLOCA 1
>> | #define HAVE_SSE2 1
>> | /* end confdefs.h.  */
>> |
>> | int
>> | main ()
>> | {
>> |
>> |   ;
>> |   return 0;
>> | }
>> configure:4543: error: in `/sw/src/fink.build/fftw3-3.3.10-1/fftw-3.3.10':
>> configure:4545: error: C compiler cannot create executables
>> I think the problem is that I moved my Xcode installation to an external drive that has spaces in it’s volume name.
>> Any suggestions on how to work around this problem, without say renaming the external drive (which would cause me endless grief editing names all over the place)...
>> Thanks,
>> Mike
> 
> Did you run `xcode-select` after you moved Xcode.app?
> 
> What's the output of `xcode-select -p` ?
> 
> Look at `man xcode-select` for the different options available. You might need to switch the path and use quotes around the "/Volumes/LaCie Thunderbolt RAID Set 1/Applications/Xcode.app" path. *Maybe* that help when the path is transferred to other uses (like in the compiler command).
> 
> Hanspeter
> 
> -- 
> "Of the 22 schools in the top 20..."
>  --Unknown

_______________________________________________
Fink-users mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users