Today, in between stuff I was supposed to be doing, I decided to start fresh with a new go at compiling Macports from source on my test Mac running the
Snow Leopard DP Build 10A96 (i.e., the project on which I spend most of my time here because hey, why not?).
I wiped the previous build from source, which I think was 2.6.4, and I went ahead with the current iteration, 2.7.1.
As with the previous, compiling was successful.
Unlike the previous, on which I couldn’t get
any port to build — not even mpstats or
neofetch — (because everything for darwin10 was intended to be Intel only), I had some success this time.
Once more, the first port I tried was mpstats (the default macports recommendation which lets the project know what ports are being requested on which platforms/versions, such as darwin10 on a ppc). I don’t know what I did differently this time, but I noticed promptly how macports, following its first run syncing its database with the repo server, was fetching a darwin10 repository for mpstats specified not for
i386
, but for
noarch
— which I parsed to mean the port isn’t written for any CPU speciality. Quite honestly, this was the first time I had ever seen a “noarch” repository for any port, ever.
Very quickly, I saw mpstats build successfully. Nice! Next up, I tried neofetch. It also grabbed a “noarch” version of the port and built successfully:
View attachment 1814386
Then my troubles began when I tried building more complex ports with multiple dependencies — such as dp48, openssl, or irssi. This is when I learnt how only some ports have a “noarch” variant for darwin10. I did some reading in the macports documentation and found there is a
keyword mention of “
supported_archs”, but I was not really able to figure out whether keywords can be specified when running a “port install” command.
I
thought I was on the right path when I found other references elsewhere mentioning how appending a “+noarch” flag to a port install might send a request for that repository, if one is available. I’m not sure whether that flag actually does anything — which here would only be useful if one already knew there was a “noarch” variant actually available for a particular port.
What I also can’t figure out is how to search for and figure out which ports are offered as both “noarch” and “darwin10”. So for now, finding the few ports which are “noarch” and also have no dependencies (when most darwin10 ports are only offered as i386/x86_64) is a bit like playing a boring game of pin-the-donkey.
But as someone who can’t code, at least I learnt this much. And now Snow Leopard for PowerPC
can have little a neofetch, as a treat.