Why some ports seem to install universal when I do not request it ?

[Christopher Jones]

Hi,

Thanks, eventually I figured that out for myself as well. I didn’t appreciate that if a port indicated it didn’t support arm, the x86_64 would be installed instead and used via rosetta etc. nice.

I  have though already found a number of ports I use indicate they only support x86_64 but this seems unnecessary as remove it they build fine for arm64, so can be removed.

cheers Chris

> On 15 Aug 2023, at 5:59 am, Joshua Root <jmr at macports.org> wrote:
> 
> On 15/8/2023 05:06, Christopher Jones wrote:
>> Hi All,
>> Just migrated from an intel to AppleSilicon machine.
>> Reinstalling MacPOrts, from scratch off course, I’ve noticed some ports get install universal, when it’s not something I have requested. e.g.
>> --->  Fetching archive for zlib
>> --->  Attempting to fetch zlib-1.2.13_0+universal.darwin_22.arm64-x86_64.tbz2 from https://packages.macports.org/zlib
>> --->  Attempting to fetch zlib-1.2.13_0+universal.darwin_22.arm64-x86_64.tbz2.rmd160 from https://packages.macports.org/zlib
>> --->  Installing zlib @1.2.13_0+universal
>> --->  Cleaning zlib
>> --->  Deactivating zlib @1.2.13_0
>> --->  Cleaning zlib
>> --->  Activating zlib @1.2.13_0+universal
>> zlib has a universal port, but its not a default one, and I didn’t request it, nor have I ever set my default settings to always install universal.
>> As I am new to apple silicon machines, is this normal ?
> 
> Most likely you installed a port that supports x86_64 but not arm64. The behaviour is the same as as when you install a port that only supports i386 on an x86_64 system.
> 
> - Josh

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20230815/374ebd11/attachment.htm>