I just ran into this error after upgrading to MacOS 13.3. I first started
seeing issues with stdio.h being missing, so I tried reinstalling Xcode
command line tools. I was then missing complex.h, so I tried reinstalling
all of Xcode. Then configure gave me the error described in this thread;
looking at config.log I found that I needed to run
sudo xcodebuild -license
and agree to the license terms. Our configure script suppresses this
suggestion (though it does suggest looking at config.log, where it appears).
Unfortunately, this didn't fix the original problem with stdio.h being
missing. The error
clang: warning: no such sysroot directory:
'/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk'
[-Wmissing-sysroot]
In file included from primecountpy/primecount.cpp:33:
In file included from /usr/local/opt/python@3.9
/Frameworks/Python.framework/Versions/3.9/include/python3.9/Python.h:25:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/stdio.h:107:15:
fatal error: 'stdio.h' file not found
#include_next <stdio.h>
^~~~~~~~~
had a link to a specific 10.15 sdk.
It turns out that after the upgrade the sdk from the old version of MacOSX
was gone. Symlinking using
sudo ln -s /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk
seems to have fixed the problem (after remembering to
source .homebrew-build-env).
Hoping that this might be helpful for people building Sage after upgrading
MacOS!
David
On Tue, Jun 21, 2022 at 12:41 PM John H Palmieri <jhpalmier...@gmail.com>
wrote:
> Have you tried reinstalling the command-line tools?
>
> On Tuesday, June 21, 2022 at 6:44:54 AM UTC-7 gcha...@vols.utk.edu wrote:
>
>> Hello,
>> I recently updated my computer and XCode, which seems to have broken my
>> ability to compile sage. I have tried fully uninstalling and reinstalling,
>> making sure to follow all the MacOS pre-installation recommendations.
>> However, I keep getting the "C compiler cannot create executables" error
>> when I try to run ./configure. Any ideas? Config log attached.
>> Thanks in advance!
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/ee864457-505a-4bb5-83c9-5268a2d832fbn%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-devel/ee864457-505a-4bb5-83c9-5268a2d832fbn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CAChs6_k8q1%3DVpApcuYugyCGRRMxi1uY8cKy7%3D-0OzcjKgqQB%2BA%40mail.gmail.com.
