py38-scipy not building on macOS 11.2

[smeingast (Stefan Meingast)]

I am not sure why, but after the latest updates to macOS I am not able to build scipy any longer. Weirdly, I get the CLT warning:

The macOS 11.2 SDK does not appear to be installed. Ports may not build correctly.

even though I completely reinstalled everything (Xcode, CLT, and even all ports). I also to not really see the issue in the log. :/

[smeingast (Stefan Meingast)]

main.log

[mf2k (Frank Schima)]

In the future, please add the port maintainer(s) to Cc (port info --maintainers py38-scipy), if any.

[nhchan]

main.log (nhchan)

[nhchan]

I have the same issue, and would like to add my main.log to the collection here.

For context, I am running macOS 11.2.3, MacPorts 2.6.4. Also, running pkgutil --pkg-info=com.apple.pkg.CLTools_Executables | grep version gives me version: 12.4.0.0.1.1610135815, although I still get the following warnings:

Warning: The macOS 11.2 SDK does not appear to be installed. Ports may not build correctly.
Warning: You can install it as part of the Xcode Command Line Tools package by running `xcode-select --install'.

I have re-installed Xcode and Command Line Tools at least 3 times, including directly downloading the installers from Apple's Developer site.

[kencu (Ken)]

it looks like you are trying to use gcc9 instead of gcc10 ... this could happen if you're upgrading.

If so, you might try instead uninstalling your current py38-scipy and then installing a fresh default version.

If everything you have is gcc9 era, and you don't specifically need gcc9, then other installed software might benefit from the same treatment.

[nhchan]

Replying to kencu:

it looks like you are trying to use gcc9 instead of gcc10 ... this could happen if you're upgrading.

If so, you might try instead uninstalling your current py38-scipy and then installing a fresh default version.

If everything you have is gcc9 era, and you don't specifically need gcc9, then other installed software might benefit from the same treatment.

Thanks for the suggestion!

I have tried switching everything to gcc10 (and attempting with the gcc10 variant), but got the same result. The only way it works is if I simply not use the gcc10 variant and let the "fresh default version" be installed (which is fine by me at the moment, but I would think the provided variants should ideally all work eventually).

[michaelld (Michael Dickens)]

I just pushed the latest NumPy, which might fix this issue. Please update your ports and try this again & let us know here if this helps.

[reneeotten (Renee Otten)]

this builds now everywhere on the buildbots, so assuming that this indeed has been fixed. As Michael said above, please give it a try and feel free to reopen this ticket if you're still experiencing issues.