Opened 5 years ago
Closed 4 years ago
#59237 closed defect (worksforme)
MacPorts fails to build on macOS Catalina
Reported by: | smeingast (Stefan Meingast) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.6.1 |
Keywords: | catalina | Cc: | |
Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
I am currently testing a fresh install of macOS Catalina on my secondary machine. I have tried to install MacPorts from source, but here already the configure step fails with:
checking for SQLite >= 3003011... configure: error: "SQLITE_VERSION_NUMBER undefined or sqlite3.h not found"
Please note that I did install Xcode (11.1), I also installed the Command Line Developer Tools, and accepted the license. I am attaching the complete configure output.
thanks for any help!
Attachments (2)
Change History (9)
Changed 5 years ago by smeingast (Stefan Meingast)
Attachment: | macports_configure.txt added |
---|
comment:3 follow-up: 4 Changed 5 years ago by jmroot (Joshua Root)
clang: error: unsupported option '-V -Wno-framework-include-private-from-public'
Looks like you are setting some unusual CFLAGS.
comment:4 Changed 5 years ago by smeingast (Stefan Meingast)
Replying to jmroot:
clang: error: unsupported option '-V -Wno-framework-include-private-from-public'Looks like you are setting some unusual CFLAGS.
Weird. I am not setting anything myself. 🤔
comment:5 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Keywords: | catalina added |
Although I can't explain the appearance of the -Wno-framework-include-private-from-public
flag in it, I'm not sure that the failure of the gcc -V
test matters; that test is supposed to fail anyway.
Still, it might be useful to check your environment variables (run env
) and make sure you don't have any variables set that would influence the build, such as CC
, CXX
, CFLAGS
, CPPFLAGS
, CXXFLAGS
, LDFLAGS
, DYLD_LIBRARY_PATH
. It's also a good idea to make sure your PATH
doesn't include non-Apple components. For example try export PATH=/usr/bin:/bin:/usr/sbin:/sbin
before configuring MacPorts. Also make sure you don't have anything in /usr/local or /Library/Frameworks.
Later in the log, I see that the compile checks seem to fail because of errors in the SDK:
In file included from conftest.c:14: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/string.h:63: In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/Availability.h:246: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/AvailabilityInternal.h:147:2: error: #endif without #if #endif /* __ENABLE_LEGACY_IPHONE_AVAILABILITY */ ^
Of course I'm sure your Xcode SDK files are fine. Is it possible that you have an old version of the command line tools? Make sure you've installed the Xcode 11.1-compatible version of the command line tools for Catalina.
Others are successfully building MacPorts 2.6.1 on Catalina so something must be different about your computer.
comment:6 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
With the release of MacPorts 2.6.2 we now have an installer package for Catalina that you could use.
comment:7 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
I'm going to close this since we haven't heard back from you and MacPorts builds fine on Catalina for us.
configure output