Opened 12 months ago
Closed 12 months ago
#67414 closed defect (fixed)
qt513-qtbase @5.13.2_9+openssl: ../bin/qmake – command not found
| Reported by: | thetrial (alabay) | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.8.1 |
| Keywords: | sierra legacy-os | Cc: | mascguy (Christopher Nielsen) |
| Port: | qt513-qtbase |
Description
This happens on two machines. So I don’t guess it is a misconfiguration in the system. Log is attached.
:info:configure /bin/sh: o: command not found :info:configure make: [../bin/qmake] Error 127 (ignored) :info:configure ./configure: line 860: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt513/qt513-qtbase/work/qtbase-everywhere-src-5.13.2/bin/qmake: No such file or directory
Attachments (1)
Change History (8)
Changed 12 months ago by thetrial (alabay)
comment:1 Changed 12 months ago by thetrial (alabay)
comment:2 Changed 12 months ago by andlabs (Pietro Gagliardi)
Looks like none of the mirrors have 5.13.2_9 binaries yet, so it's falling back to building from source, which is failing for different reasons.
What version of Xcode do you have? It looks like the MacPorts patch is trying to force the use of the macosx10.12 SDK, but Xcode 9.2 only ships with the macosx10.13 SDK.
I was able to work around this by forking macports-ports/aqua/qt513 locally (using portindex) and changing the instance of __MACPORTS_MAC_SDK__ in files/patch-mkspecs.diff to macosx10.13.
https://trac.macports.org/ticket/53601 might be a related issue? There's probably a MacPorts config file that needs changing on our machines to match the installed Xcode.
Note that the lack of binaries applies to all OS versions, so it will build from source even on Ventura.
comment:3 Changed 12 months ago by thetrial (alabay)
I have Xcode 9.2. This SDK thing happened under macOS 10.11 with 10.11 versus 10.12. It’s annoying that this catches up with 10.12 versus 10.13.
comment:4 Changed 12 months ago by mascguy (Christopher Nielsen)
| Cc: | mascguy added |
|---|
comment:5 Changed 12 months ago by thetrial (alabay)
We had that before … #66549.
I did a sudo port install MacOSX10.12.sdk (with all necessary donwload and placement stuff …) and then first copied MacOSX10.12.sdk to /Library/Developer/CommandLineTools/SDKs/ and /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/.
Now it builds and builds, let’s see, if it works.
Next, I’d try sudo ln -s /opt/local/Developer/SDKs/MacOSX10.12.sdk /Library/Developer/CommandLineTools/SDKs/ and sudo ln -s /opt/local/Developer/SDKs/MacOSX10.12.sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs … if.
comment:6 Changed 12 months ago by thetrial (alabay)
Well, it ran through. Even with symbolic linked SDK. So this is a hacky solution to it. But this is not out-of-the-box. The question is, if there is another way to prevent this cul-de-sac.
comment:7 Changed 12 months ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
By the way … this hassle broke more. KeePassXC 2.7.4 is not working anymore and Macports claims that 1 port and 3 files are broken. It wants to rebuild qt513-qtbase @5.13.2+openssl – what of course fails. So this is a catch-22 trap. I’m not sure which other qt-stuff had been updated before, but it’s quite sordid that en error of a port breaks the installation. So maybe the order of updates is not suitable. Macports cannot easily return to a former state.