On Feb 20, 2025, at 12:18, Riccardo Mottola wrote: > > It doesn't explain why libpc shouldn't build universal, but the real > question, where is all this universal coming from? I never requested it on > this system. Can I trace the ports(s) pulling it in? > a quick grep for universal in ports shoes a lot of active: > python310, libomp, sqlite3, xz, libffi, libiconv, expat and even > clang-11-boostrap
Had you at some point tried to install a Wine port? That's one of the more common reasons why you would have its dependencies installed universal. The Wine ports no longer support old macOS versions so if that was the reason you may as well reinstall those ports without the universal variant to save yourself the trouble.
