Opened 19 months ago

Last modified 19 months ago

#66145 closed defect

qt5-qtbase: configure Failed to resolve SDK path for 'macosx13' — at Version 9

Reported by: boccio-john Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: qt5-qtbase

Description (last modified by jmroot (Joshua Root))

Got past problems in ticket #66138 by following suggestions to open Xcode once before starting.

Now after another 1-1/2 hours of compiling (total of 4-1/2) I got another error

--->  Fetching archive for qt5-qtbase
--->  Attempting to fetch qt5-qtbase-5.15.6_0+openssl.darwin_22.arm64.tbz2 from https://packages.macports.org/qt5-qtbase
--->  Attempting to fetch qt5-qtbase-5.15.6_0+openssl.darwin_22.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/qt5-qtbase
--->  Attempting to fetch qt5-qtbase-5.15.6_0+openssl.darwin_22.arm64.tbz2 from https://mse.uk.packages.macports.org/qt5-qtbase
--->  Fetching distfiles for qt5-qtbase
--->  Attempting to fetch qtbase-everywhere-opensource-src-5.15.6.tar.xz from https://distfiles.macports.org/qt5
--->  Verifying checksums for qt5-qtbase                                         
--->  Extracting qt5-qtbase
--->  Applying patches to qt5-qtbase
--->  Configuring qt5-qtbase
Error: Failed to configure qt5-qtbase: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_qt5/qt5-qtbase/main.log for details.

I have attached the main.log file

Change History (11)

Changed 19 months ago by boccio-john

Attachment: main.log added

main.log from error

comment:1 Changed 19 months ago by kencu (Ken)

I didn't have too much trouble on Ventura Intel, FWIW:

% port -v installed octave
The following ports are currently installed:
  octave @7.2.0_1+app+docs+gfortran+graphicsmagick+openblas+qt5+sound+sundials (active) requested_variants='' platform='darwin 22' archs='x86_64' date='2022-10-27T20:21:00-0700'

comment:2 Changed 19 months ago by kencu (Ken)

You are having an issue with qt ports that we thought we had fixed, but apparently haven't completely fixed.

configure Failed to resolve SDK path for 'macosx13'

I am pondering a much simpler fix for this issue, that the rather more complicated and apparently not always effective fix we are currently using.

For now, please clean any partially-built ports (the easiest way might be to use "sudo port -v reclaim" and then say no to everything up until it asks you if you want to delete all the build directories, and then say yes) and then make sure your ports tree is fully up to date so you pick up all the Ventura fixes that have been put into the tree over the past 72 hours.

sudo port -v reclaim
sudo port selfupdate

and then try again, and post up any logs of ports that then fail.

Ventura is new. There are always some issues to be expected with new systems. People who really live and die for a specific port like Octave tend to hang back a few months on updates and wait to see that port has been built by the buildbots before updating.

comment:3 in reply to:  1 Changed 19 months ago by boccio-john

Replying to kencu:

I didn't have too much trouble on Ventura Intel, FWIW:

% port -v installed octave
The following ports are currently installed:
  octave @7.2.0_1+app+docs+gfortran+graphicsmagick+openblas+qt5+sound+sundials (active) requested_variants='' platform='darwin 22' archs='x86_64' date='2022-10-27T20:21:00-0700'

I am using Mac Ventura on a Mac Studio M1 Max.

Do they test the ports and various machines?

I am at a total loss as to what I can do when these errors occur.

comment:4 Changed 19 months ago by kencu (Ken)

Well yes we do, but octave has a lot of supporting ports, and Ventura is very new, and many MacPorts regulars haven't bought or have access to an arm Mac yet to fix issues that might arise.

You are breaking new ground, but you'll have success in the end I believe. Are you reasonably facile with basic computer skills? For example, if I asked to to:

bbedit `port file qt5-qtbase`

and add a line of text into the Portfile that opens, then save the file, do you feel you could do something such as that?

comment:5 in reply to:  4 Changed 19 months ago by boccio-john

Replying to kencu:

Well yes we do, but octave has a lot of supporting ports, and Ventura is very new, and many MacPorts regulars haven't bought or have access to an arm Mac yet to fix issues that might arise.

You are breaking new ground, but you'll have success in the end I believe. Are you reasonably facile with basic computer skills? For example, if I asked to to:

bbedit `port file qt5-qtbase`

and add a line of text into the Portfile that opens, then save the file, do you feel you could do something such as that?

I am certainly not an expert on Unix.

Yes, I can do something like that illustrated command.

Thanks.

John

comment:6 Changed 19 months ago by kencu (Ken)

Port: qt5-qtbase added
Summary: continuing saga of octave installqt5-qtbase: configure Failed to resolve SDK path for 'macosx13'

Changed 19 months ago by boccio-john

Attachment: main.2.log added

texlive-bin fail main.log

comment:7 Changed 19 months ago by kencu (Ken)

So this is supposed to be fixed, and did work for a number of folks, but not everyone. We are trying to sort out why not.

As above, if after cleaning all builds (possibly using reclaim as above) and updating all your portfiles to the latest versions, you still get the build error, add configure.sdk_version with nothing specified after it on the line to the qt5-qtbase Portfile, so it looks like below:

bbedit `port file qt5-qtbase`

change this:

homepage            https://www.qt.io

set qt_version      5.15.6

to this:

homepage            https://www.qt.io
configure.sdk_version
set qt_version      5.15.6

that should get you going. It shouldn't be needed, but anyway, if it is needed for you, please let us know it worked.

comment:8 Changed 19 months ago by kencu (Ken)

wait, hold on -- you are posting a build failure for texlive-bin now.

Did qt5-qtbase build for you, in the end?

And now you have a different port that is not building?

(The way these tickets work is that one ticket is for one build failure on one port. Otherwise -- insanity looms.)

comment:9 Changed 19 months ago by jmroot (Joshua Root)

Description: modified (diff)
Note: See TracTickets for help on using tickets.