Open barracuda156 opened 2 months ago
Probably because it was set that way in the Portfile I based this one on. Is it used for anything other than controlling +universal builds?
It just refuses to try installing, complaining about being x86-only.
Ah, indeed, even 2.7.1 already had a reject feature. It's a bit stupid that no override exists for this. I'll add one, but in the meantime just comment out the offending line.
BTW, pkgconf is one of those ports that have no clear use; I probably made it because some other piece of software I wanted to try (and never made it to getting a port) needed it.
I thought to install it in place of pkgconfig, since MacPorts supports that, and pkgconfig
fails to build on riscv (well, by default at least, I did not get to fixing it yet).
On Friday August 23 2024 04:58:23 Sergey Fedorov wrote:
I thought to install it in place of pkgconfig, since MacPorts supports that
I'm not certain pkgconf is a perfect drop-in replacement of pkgconfig . How does MP allow using another implementation, you mean the path:-style depspec mechanism? That only works if an alternative port installs an alternative version of the required resources.
But did you notice the runtime dependency of pkgconf? ;)
Why
pkgconf
is set tosupported_archs x86_64
?