BUG: Build failure with Xcode 12
See original GitHub issueXcode 12 for OS X was just released, and I can’t build scipy with it. The command pip3 install . -v --user fails, ending with
error: Command "clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -I/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Tk.framework/Versions/8.5/Headers -DUSE_VENDOR_BLAS=1 -Iscipy/sparse/linalg/dsolve/SuperLU/SRC -I/private/var/folders/cp/n8wtqs490tq5psknff1hv9qr0000gn/T/pip-build-env-k4q2ai5g/overlay/lib/python3.8/site-packages/numpy/core/include -c scipy/sparse/linalg/dsolve/SuperLU/SRC/clacon2.c -o build/temp.macosx-10.15-x86_64-3.8/scipy/sparse/linalg/dsolve/SuperLU/SRC/clacon2.o -MMD -MF build/temp.macosx-10.15-x86_64-3.8/scipy/sparse/linalg/dsolve/SuperLU/SRC/clacon2.o.d" failed with exit status 1
Building wheel for scipy (PEP 517): finished with status 'error'
ERROR: Failed building wheel for scipy
Failed to build scipy
ERROR: Could not build wheels for scipy which use PEP 517 and cannot be installed directly
This may be the same issue as https://github.com/scipy/scipy/issues/12656 — at least the error at the end is the same — but that issue was closed while only providing the suggestion to use a different compiler.
I am using Xcode 12, plus homebrew’s Python 3.8, pip3, and gfortran. Unfortunately, I am really trying to figure out how to get this to build in Sage (sagemath.org), and using a gcc toolchain instead of clang would be, at the least, very inconvenient.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:20 (16 by maintainers)
Top Results From Across the Web
Xcode 12 Build failed, error: circular reference
Our project compiles and runs fine on Xcode 11. However, when I compile with Xcode 12, it tells me <unkown>0: error: circular reference...
Read more >Xcode: Build Failed, but no error messages - Stack Overflow
Build operation failed without specifying any errors. Individual build tasks may have failed for unknown reasons. One possible cause is if there are...
Read more >Xcode 12 fails to build a project containing Batch
After updating, your project might fail to build if you update to Xcode's recommended build settings. The error looks like this: ❌ ld:...
Read more >Workaround: Xcode 13 failure after running framework project ...
I discovered a bug in Xcode 13 where tests crash for framework projects, preventing unit tests from successfully running on CI.
Read more >How to fix the error "The developer of this app needs to update ...
After upgrading to iOS 15, you may see an error in applications built with XCode 12.4 or earlier that were previously running on...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Should be fixed on
masterand upcoming1.5.4release.The TODOs here seem to be:
Determine what patch is needed for
masterbranch. I was, for some reason, under the impression this was fixed formasterbut not the1.5.xmaintenance branch. gh-12937 suggests thatmasterhas issues as well unless the CI there is using yet another version of XCode or something? (the CI failed there even before my patching attempt). Conversely, when I’ve tried local builds ofmasterwith XCode 12 they seem to work just fine.We seem pretty close on a patch that will fix the issue for
1.5.xbased on the feedback from i.e., @adamjstewart above in gh-12957. What I might do there is turn on the same MacOS Python 3.9 CI that is failing in gh-12937 and if that passes we can maybe move forward with 1.5.x in that regard at least. (We may be able to remove the qhull shims though, since a simpler one should have been backported). This patch actually does show the fail before/fix after applying when I test locally with XCode 12.