Opened 5 years ago
Closed 2 years ago
#60062 closed defect (worksforme)
selfupdate fails with Xcode 10.1 on macOS 10.13 because it uses the 10.14 SDK which doesn't have i386 bits
Reported by: | nikgervae | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.5.4 |
Keywords: | highsierra | Cc: | jmroot (Joshua Root) |
Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
I am on MacOS High Sierra 10.13.6, trying to update my ports. I ran sudo port selfupdate
and then, I ran sudo port upgrade outdated
and got this output:
Error: Unable to open port: invalid command name "compiler.cxx_standard" Error: Follow https://guide.macports.org/#project.tickets to report a bug.
If I try sudo port upgrade installed
, I instead get this error:
Error: Unable to open port: can't set "compiler.blacklist": invalid command name "compiler.command_line_tools_version" Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Attachments (1)
Change History (14)
comment:2 Changed 5 years ago by nikgervae
Description: | modified (diff) |
---|
comment:3 Changed 5 years ago by jmroot (Joshua Root)
Cc: | jmroot added |
---|
Changed 5 years ago by nikgervae
Attachment: | port-log.txt added |
---|
Output of sudo port -d selfupdate
as requested by engineer
comment:4 Changed 5 years ago by nikgervae
Output of sudo port -d selfupdate
attached. It looks like the build system is trying to use the SDK for 10.14, even though I am running 10.13, and can't find the architecture i386.
comment:5 Changed 5 years ago by nikgervae
And sure enough, when I go to /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/, the only SDK in that directory is for 10.14. I have no idea how that happened. Xcode's version is 10.1, and apparently I should be running version 8.3.3 or 9.0. I'll see if I can download one of those. Good thing Apple makes it SO EASY to do so:
Safari can’t open the page “https://idmsa.apple.com/IDMSWebAuth/signin?appIdKey=891bd3417a7776362562d2197f89480a8547b108fd934911bcbea0110d07f757&path=%2Faccount%2F&rv=1” because Safari can’t establish a secure connection to the server “idmsa.apple.com”
comment:6 Changed 5 years ago by jmroot (Joshua Root)
Xcode 10.1 should be fine on High Sierra, as long as you have the Command Line Tools installed, which should provide the 10.13 SDK.
comment:7 Changed 5 years ago by nikgervae
No luck. I even tried reinstalling the command-line tools, and all I have is the 10.14 SDK. I'll see if a friend can access the developer login and get the installer package.
comment:8 Changed 5 years ago by jmroot (Joshua Root)
The place to put the 10.13 SDK when you get it is /Library/Developer/CommandLineTools/SDKs/MacOSX10.13.sdk
BTW.
comment:9 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Component: | ports → base |
---|---|
Description: | modified (diff) |
comment:10 Changed 5 years ago by jmroot (Joshua Root)
Although come to think of it, normally the CLTs should install /usr/include on 10.13, and if that exists, an SDK shouldn't be used at all.
comment:11 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | highsierra added |
---|---|
Summary: | port 2.5.4: Error: Unable to open port: invalid command name "compiler.cxx_standard" → selfupdate fails with Xcode 10.1 on macOS 10.13 because it uses the 10.14 SDK which doesn't have i386 bits |
Agreed. On 10.13, it should not be trying to use an SDK; it should be using /usr/include. The fact that it's not suggests that you don't have /usr/include. Even though you said above that you already tried reinstalling the command-line tools, please try it again. Make sure you've downloaded "Command Line Tools (macOS 10.13) for Xcode 10.1" from https://developer.apple.com/download/more/?=macOS%2010.13
comment:12 Changed 4 years ago by nikgervae
Safari had been failing repeatedly to even load the Apple developer page, but I switch to Firefox and finally managed to download and install the package. All is well now. Thanks for the URL to the item I needed to install, it saved some bother.
comment:13 Changed 2 years ago by jmroot (Joshua Root)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
If you are running MacPorts 2.5.4, that is the problem: it is not compatible with the current ports. You need to update to the current version, MacPorts 2.6.2. If selfupdate is not doing that for you, run
sudo port -d selfupdate
to see what is going wrong.