On 25/2/2025 11:57, Riccardo Mottola wrote:
Perhaps I expressed myself unclearly. I intend that there is no issue on
the build machine, but I have universal on my user system. So if some
automatic dependency would kick in to make it universal, it should
happen there too, shouldn't it?
Universal dependencies do get installed on the buildbot sometimes.
port installed | grep universal
bzip2 @1.0.8_0+universal (active)
expat @2.6.4_0+universal (active)
gettext-runtime @0.22.5_0+universal (active)
libedit @20250104-3.1_0+universal (active)
libffi @3.4.6_1+universal (active)
libiconv @1.17_0+universal (active)
libomp @19.1.7_0+universal (active)
ncurses @6.5_0+universal (active)
openssl @3_22+universal (active)
openssl3 @3.4.1_0+universal (active)
sqlite3 @3.49.1_0+universal (active)
xz @5.6.4_0+universal (active)
zlib @1.3.1_0+universal (active)
I imagine however that they will not rebuild by themselves as non-
universal? I did not enough to heal things, but the universal might
propagate again, wouldn't it?
I'ld like to rebuild these without breaking dependencies or rebuilding
uninstalling too much...
As Ryan mentioned, just install them without +universal:
sudo port install --unrequested libiconv gettext-runtime ncurses xz
bzip2 zlib expat openssl3 openssl libedit sqlite3 libffi libomp
The universal versions will be deactivated.
If you never want anything to automatically install with +universal
again, you can clear universal_archs in macports.conf, and then you will
get an error if a universal dependency is needed. If you decide you do
want to allow it for something, you can restore universal_archs to its
default either temporarily or permanently.
- Josh
