On Wednesday June 15 2022 17:10:01 Christopher Jones wrote: >what about configure.universal_archs though, have you set that to have > 1 >entry ? thats what base cares about, hence the "due to < 2 supported >universal_archs
Ahhhh! That works, indeed. It seems that this variable is empty when the portfile is parsed but initialised with the OS-supported archs from `supported_archs`, is that correct? That's not exactly what `guide.macports.org` states - for `universal_archs`, it doesn't discuss `configure.universal_archs`. IMHO it's a bit unexpected that there are 2 settings to control what architectures a port supports! R.
