HI Josh;
Thank you! I am now exclusively arm64 :-)
Ken
On Sun, May 28, 2023 at 5:05 PM Joshua Root wrote:
>
> Hi Ken,
>
> Your can see the architecture(s) each port is built for with 'port -v
> installed'. The ones of concern on an Apple Silicon system will have
> archs='x86_64'.
>
> - Josh
Hi Ken,
Your can see the architecture(s) each port is built for with 'port -v
installed'. The ones of concern on an Apple Silicon system will have
archs='x86_64'.
- Josh
On 29/5/2023 09:55, Kenneth Wolcott wrote:
HI Josh;
Is it possible to find out what ports that I have installed that
HI Josh;
Is it possible to find out what ports that I have installed that
would fail to upgrade due to not supporting the M1 chip? If, so what
command would I issue so that I could determine the risk involved of
doing that massive upgrade operation?
Thanks,
Ken Wolcott
On Sun, May 28, 2023
On Mon, 24 Apr 2023, Dave Horsfall wrote:
[ Disabling "+universal" ]
Yes, that seems to be it; thanks. Now, is there a way to globally
disable "universal" without cleaning every port and rebuilding with
"-universal"?
You don't have to rebuild everything, but there's no getting around
On Mon, 24 Apr 2023, Dave Horsfall wrote:
> [ Disabling "+universal" ]
>
> Yes, that seems to be it; thanks. Now, is there a way to globally
> disable "universal" without cleaning every port and rebuilding with
> "-universal"?
Anyone?
-- Dave
On Sun, 16 Apr 2023, Richard L. Hamilton wrote:
> That may mean you tried to install glib2 with +universal but did not
> previously install dbus with +universal. Or something like that which
> has similar results.
[...]
Yes, that seems to be it; thanks. Now, is there a way to globally
FYI I have had good luck with opencore legacy patcher on several machines.
A macbookpro 9,2 can run the current Ventura, for example, very nicely
(upgraded to 16GB Ram).
Some machines don't fare as well -- a macbookpro 9,1 I tried to upgrade
struggles.
K
On 2023-04-18, at 11:17 AM, Eldrid
Some "modern" builds can't build on older MBP arch. I have a similar MBP
with HS - where e.g. homebrew requires a newer XCode that in turn requires
a newer macOS (with newer hardware - Apple's money-making tactics will
continue with the newer MBPs). My work client projects required a newer
setup -
if glib2 now links against dbus (and it seems at least one test does) then dbus
will need to be added to the build deps of glib2 so that macports can work out
the architecture matching needed to prevent this.
I can't see any indication that any of the installed glib2 files link against
dbus,
> Early MacBook Pro (13", mid 2010), High Sierra 10.13.6 (as far as it will
> go).
>
> When doing my weekly port upgrade, it bombs out with:
>
>---> Building glib2
>Error: Failed to build glib2: command execution failed
>Error: See
>
Early MacBook Pro (13", mid 2010), High Sierra 10.13.6 (as far as it will
go).
When doing my weekly port upgrade, it bombs out with:
---> Building glib2
Error: Failed to build glib2: command execution failed
Error: See
11 matches
Mail list logo
