On Mon, Jun 12, 2023 at 10:25:47PM -0400, "Richard L. Hamilton"
wrote:
> "On macOS 10.14, iTerm2 @3.4.19 requires Xcode 11.0 or later but you have
> Xcode 10.3."
>
> 11.3.1 is the newest Xcode for Mojave.
>
> Is there any known downside to Xcode 11.3.1 on Mojave rather than the
> 10.3 I have
After updating Xcode while keeping the same OS, should one delete and reinstall
all MacPorts packages?
No, there's no reason to do that if you have only changed the Xcode version.
- Josh
After updating Xcode while keeping the same OS, should one delete and reinstall
all MacPorts packages?
Thanks
Franco
> On 13 Jun 2023, at 21:33, Ken Cunningham
> wrote:
>
>
> On 2023-06-12, at 7:25 PM, Richard L. Hamilton wrote:
>
>> "On macOS 10.14, iTerm2 @3.4.19 requires Xcode 11.0 or
On 2023-06-12, at 7:25 PM, Richard L. Hamilton wrote:
> "On macOS 10.14, iTerm2 @3.4.19 requires Xcode 11.0 or later but you have
> Xcode 10.3."
>
> 11.3.1 is the newest Xcode for Mojave.
>
> Is there any known downside to Xcode 11.3.1 on Mojave rather than the 10.3 I
> have on there now?
I keep older macOS versions on VMs or old hardware for features they still had
(Snow Leopard: Rosetta, Mojave: 32-bit support), even with other systems
running the latest.I do NOT surf the web or use social media on the old ones!
So sometimes I have questions regarding older versions.
> On Jun
Interesting options to upgrade macOS itself on "unsupported hardware":
https://dortania.github.io/OpenCore-Legacy-Patcher/START.html
https://dortania.github.io/OpenCore-Legacy-Patcher/MODELS.html
On Tue, 13 Jun 2023, 04:26 Richard L. Hamilton, wrote:
> "On macOS 10.14, iTerm2 @3.4.19 requires
"On macOS 10.14, iTerm2 @3.4.19 requires Xcode 11.0 or later but you have Xcode
10.3."
11.3.1 is the newest Xcode for Mojave.
Is there any known downside to Xcode 11.3.1 on Mojave rather than the 10.3 I
have on there now? Space is tight, so I'm not sure I want both.
And will I need 11.3.1
On 2021-01-07 2:45 p.m., Davide Liessi wrote:
Dear Ken,
I decided to upgrade to Xcode 10.1.
I was able to install qt5-qtwebengine, but the build stopped several
times due to errors of the kind
ninja: fatal: posix_spawn: Too many open files
ninja: fatal: pipe: Too many open files
I adjusted
Dear Ken,
Il giorno sab 2 gen 2021 alle ore 19:10 Ken Cunningham
ha scritto:
> Right now, you could say the only immediate visible advantage of
> upgrading to Xcode10 is to build qt5-qtwebengine version 5.15.2 on
> 10.13
I decided to upgrade to Xcode 10.1.
I was able to install qt5-qtwebengine,
On 2021-01-01 3:46 p.m., Ken Cunningham wrote:
On Jan 1, 2021, at 3:35 PM, Davide Liessi wrote:
Il giorno sab 2 gen 2021 alle ore 00:12 Ken Cunningham
ha scritto:
IMO — just upgrade yourself to Xcode 10 (like everyone else has done) and the
buildbot can stay on Xcode 9.
There is one
Davide Liessi writes:
> I could remove py-pyqt-webengine from frescobaldi's dependencies (two
> components would stop working, but the rest would continue) and
> suggest in the latter's notes to install the former in order to get
> full functionality, but I would prefer to keep it.
Sigil also
> On Jan 1, 2021, at 3:35 PM, Davide Liessi wrote:
>
> Il giorno sab 2 gen 2021 alle ore 00:12 Ken Cunningham
> ha scritto:
>> IMO — just upgrade yourself to Xcode 10 (like everyone else has done) and
>> the buildbot can stay on Xcode 9.
>
> There is one port (and its dependencies, of
Il giorno sab 2 gen 2021 alle ore 00:12 Ken Cunningham
ha scritto:
> IMO — just upgrade yourself to Xcode 10 (like everyone else has done) and the
> buildbot can stay on Xcode 9.
There is one port (and its dependencies, of course) that I need to
build with the universal variant: lame.
Does
> On Jan 1, 2021, at 2:24 PM, Davide Liessi wrote:
>
> Il giorno mar 29 dic 2020 alle ore 00:35 Ryan Schmidt
> ha scritto:
>> I intentionally keep most of the buildbot workers' Xcode versions at the
>> last version that contains the SDK that matches the OS version. On macOS
>> 10.13, that's
Il giorno mar 29 dic 2020 alle ore 00:35 Ryan Schmidt
ha scritto:
> I intentionally keep most of the buildbot workers' Xcode versions at the last
> version that contains the SDK that matches the OS version. On macOS 10.13,
> that's Xcode 9.4.1.
How would you propose to solve the QtWebEngine
DK that matches the OS version. On macOS
>> 10.13, that's Xcode 9.4.1.
>
> I do fully get this idea, however:
>
> Once Xcode 10 came out, 10.13 users around the world moved to use it. 90% of
> users are on homebrew, and they do not hold back their Xcode version on 10.1
I do fully get this idea, however:
Once Xcode 10 came out, 10.13 users around the world moved to use it. 90% of
users are on homebrew, and they do not hold back their Xcode version on 10.13
to Xcode 9.
So —
If software had an issue artificially finding 10.14 features that were not
supported on 1
On Dec 27, 2020, at 10:11, Ken Cunningham wrote:
> However, I would float the idea it's time the buildbot and all 10.13 users
> moved to Xcode 10.
>
> Xcode 10's issues have largely been worked around by this point it seems,
> although there a couple of stragglers still.
I intentionally
Il giorno dom 27 dic 2020 alle ore 20:49 Ken Cunningham
ha scritto:
> Should be a ticket if not one already I guess.
I opened https://trac.macports.org/ticket/61921.
> Could you try forcing a macports-clang compiler like 9.0 and see if that
> works?
I'll try and report the results in the
> WARNING: QtWebEngine requires at least version 10.0.0, but using Xcode
> version 9.4.1.
Should be a ticket if not one already I guess.
I was wondering when we updated qt5 if that might happen to those who have held
back their Xcode on 10.13 systems. All my systems use the current
Hi.
The port qt5-qtwebengine currently fails on macOS 10.13 because
nothing is built.
The configure phase ends with the following warnings:
WARNING: QtWebEngine requires at least version 10.0.0, but using Xcode
version 9.4.1.
WARNING: QtPdf requires at least version 10.0.0, but using Xcode
On Oct 31, 2017, at 10:07, dan d. wrote:
> I reinstalled my osx - Yosemite.
>
> I downloaded the commandline tools of xcode to use with macports.
>
> I get a message saying xcode could not be found, however ports are installed.
>
> I aim to get the xcode from the app store, 12something as I
Hello,
I reinstalled my osx - Yosemite.
I downloaded the commandline tools of xcode to use with macports.
I get a message saying xcode could not be found, however ports are installed.
I aim to get the xcode from the app store, 12something as I recall.
Will it work in Yosemite or do I need
23 matches
Mail list logo
