Opened 4 years ago
Last modified 2 years ago
#62190 assigned defect
qt58-qtsvg: builds failing for 10.15 and 11: could not resolve SDK path
Reported by: | mascguy (Christopher Nielsen) | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | qt58-qtsvg |
Description (last modified by mascguy (Christopher Nielsen))
This port is failing to build, blocking downstream qt58-* ports.
Project ERROR: Could not resolve SDK Path for 'macosx10.15'
Project ERROR: Could not resolve SDK Path for 'macosx11.0'
While older build history has aged out, it looks like binaries exist for 10.9 through 10.14. So that's good news.
https://packages.macports.org/qt58-qtsvg:
qt58-qtsvg-5.8.0_0.darwin_18.x86_64.tbz2.rmd160 2018-10-12 12:20 512 qt58-qtsvg-5.8.0_0.darwin_18.x86_64.tbz2 2018-10-12 12:20 142K qt58-qtsvg-5.8.0_0.darwin_17.x86_64.tbz2.rmd160 2017-10-05 09:54 512 qt58-qtsvg-5.8.0_0.darwin_17.x86_64.tbz2 2017-10-05 09:54 141K qt58-qtsvg-5.8.0_0.darwin_16.x86_64.tbz2.rmd160 2017-10-02 03:44 512 qt58-qtsvg-5.8.0_0.darwin_16.x86_64.tbz2 2017-10-02 03:44 142K qt58-qtsvg-5.8.0_0.darwin_15.x86_64.tbz2.rmd160 2017-10-02 04:21 512 qt58-qtsvg-5.8.0_0.darwin_15.x86_64.tbz2 2017-10-02 04:21 145K qt58-qtsvg-5.8.0_0.darwin_14.x86_64.tbz2.rmd160 2017-10-02 03:47 512 qt58-qtsvg-5.8.0_0.darwin_14.x86_64.tbz2 2017-10-02 03:47 145K qt58-qtsvg-5.8.0_0.darwin_13.x86_64.tbz2.rmd160 2017-10-01 20:25 512 qt58-qtsvg-5.8.0_0.darwin_13.x86_64.tbz2 2017-10-01 20:25 144K
Change History (7)
comment:1 Changed 4 years ago by mascguy (Christopher Nielsen)
Port: | qt58-qtsvg added; qt58-svg removed |
---|
comment:2 Changed 4 years ago by mascguy (Christopher Nielsen)
Description: | modified (diff) |
---|---|
Summary: | qt58-qtsvg: builds failing: could not resolve SDK path → qt58-qtsvg: builds failing for 10.15 and 11: could not resolve SDK path |
comment:3 Changed 4 years ago by kencu (Ken)
comment:4 Changed 4 years ago by mascguy (Christopher Nielsen)
I haven't tried fixing the issue, but the SDK path issue could be the only problem.
But if it's not worth fixing, should we update the port to set known_fail
for macOS releases beyond 10.14...?
comment:5 Changed 3 years ago by jmroot (Joshua Root)
comment:6 Changed 2 years ago by chrstphrchvz (Christopher Chavez)
comment:7 Changed 2 years ago by chrstphrchvz (Christopher Chavez)
Note: See
TracTickets for help on using
tickets.
the LTS version of qt5 was 5.9.
I don't think anyone is likely going to get too motivated to fix qt58 for 10.15+ ...