Failure to install qt5-qtwebengine on Apple Silicon (...somehow solved downgrading Xcode)
Franco Vaccari
fvaccari at me.com
Mon Dec 16 11:13:10 UTC 2024
Today I successfully installed qt5-qtwebengine, and py312-spyder after that, by going back from Xcode 16.2 to 16.1, downgrading CLT’s as well.
What I did was:
Rename Xcode.app —> Xcode162.app in /Applications
Rename Developer —> Developer162 in /Library
Install Xcode version 16.1 (downloaded from developer.apple.com <http://developer.apple.com/>)
Install Command Line Tools 16.1 (downloaded from developer.apple.com <http://developer.apple.com/>)
and then
sudo xcodebuild -license
sudo port clean qt5-qtwebengine
sudo port install qt5-qtwebengine (successful)
sudo port install py312-spyder (successful)
So apparently Xcode 16.2 was the culprit, but with it more than 900 ports were successfully installed, and just qt5-qtwebengine failed.
I have saved the log files for both the unsuccessful (Xcode 16.2) and successful (Xcode 16.1) installations of qt5-qtwebengine. Should I file a bug report for qt5-qtwebengine attaching them to the report, or is this something pertaining to upstream or up to Apple?
And finally, is it a problem to have most of the ports installed using Xcode 16.2 and some ports using Xcode 16.1?
Thanks
Franco
> On 15 Dec 2024, at 18:46, Franco Vaccari <fvaccari at me.com> wrote:
>
> Installation of py312-spyder has just failed on my system (Mac OS 15.2 on Apple Silicon, Xcode 16.2, CLT’s 16.2.0.0.1.1733547573) due to failure to install qt5-qtwebengine.
>
> I didn’t expect this problem since a couple of days ago I successfully installed py312-spyder on another similar machine, but now that I think about it that machine was at Mac OS 15.1 and Xcode 16.1 at the time, and it was updated to Mac OS 15.2 and Xcode 16.2 *after* installing all the ports.
>
> In the qt5-qtwebengine log file the first error appears at step 3009. I’m ready to file a bug report with the full 5.2 MB log file, but I’m not sure if it belongs to qt5-qtwebengine or to one of its dependencies, since for instance ../../3rdparty/chromium/third_party/freetype/src/src/gzip/ftgzip.c is mentioned.
>
> What should be the correct way of reporting this? Below is the part of log relative to step 3009.
>
> Thanks
>
> Franco
>
> <SNIP>
>
>
>
More information about the macports-users
mailing list