[MacPorts] #59094: Error after updating XCode to 11.0
MacPorts
noreply at macports.org
Wed Sep 25 22:56:19 UTC 2019
#59094: Error after updating XCode to 11.0
-----------------------+--------------------
Reporter: eisGeist | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.6.0
Resolution: | Keywords:
Port: |
-----------------------+--------------------
Comment (by cluesch):
I had the same issue after running the XCode upgrade, the log-file in
question would be
{{{/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base/config.log}}}
which contains the following helpful message:
{{{
You have not agreed to the Xcode license agreements, please run
'xcodebuild -license' (for user-level acceptance) or 'sudo xcodebuild
-license' (for system-wide acceptance) from within a Terminal window to
review and agree to the Xcode license agreements.
}}}
So you have to run {{{sudo xcodebuild -license}}} again after the upgrade,
as you have on initial install of XCode. The problematic part is actually
that {{{selfupdate}}} fails silently, because without the license accepted
it does:
{{{
localhost% sudo port selfupdate
---> Updating MacPorts base sources using rsync
MacPorts base version 2.5.4 installed,
MacPorts base version 2.6.0 downloaded.
---> Updating the ports tree
---> MacPorts base is outdated, installing new version 2.6.0
Installing new MacPorts release in /opt/local as root:admin; permissions
0755
localhost%
}}}
Notice that there is no error, but it actually doesn't do anything either,
the error will just be in the log file. If you accept the license, it will
go through:
{{{
localhost% sudo port selfupdate
'---> Updating MacPorts base sources using rsync
MacPorts base version 2.5.4 installed,
MacPorts base version 2.6.0 downloaded.
---> Updating the ports tree
---> MacPorts base is outdated, installing new version 2.6.0
Installing new MacPorts release in /opt/local as root:admin; permissions
0755
Not all sources could be fully synced using the old version of MacPorts.
Please run selfupdate again now that MacPorts base has been updated.
localhost%
}}}
However now you will have a new warning whenever you compile something, I
guess this is a follow-on issue from the new SDK or SDK selection in the
configuration:
{{{
localhost% sudo port upgrade outdated
Warning: Unable to determine location of the macOS 10.14 SDK. Using the
default macOS SDK.
Warning: Unable to determine location of the macOS 10.14 SDK. Using the
default macOS SDK.
Warning: Unable to determine location of the macOS 10.14 SDK. Using the
default macOS SDK.
---> Computing dependencies for openssl
}}}
--
Ticket URL: <https://trac.macports.org/ticket/59094#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list