[Toybox] [PATCH 1/2] macOS: use getconf rather than nproc for portability.

[enh]

On Wed, Nov 28, 2018 at 5:33 PM Rob Landley <rob at landley.net> wrote:
>
> On 11/28/18 7:11 PM, enh wrote:
> > yeah, bitrot is my big fear too. i really don't want to have to
> > actually get a mac. (even if i'm not paying for it, this current
> > macbook pro genuinely is the most awful laptop i've ever used.)
> >
> > but i suspect i could always just update the mac toybox prebuilt "on
> > demand", which i assume would work out to "once every couple of years
> > or so". obviously i'll admit that to the build folks up front though
> > :-)
>
> Meanwhile I continue to ponder porting android to Hexagon and such, and would
> want it to "just work" as much as possible. (Yeah bionic would need new stuff,
> but llvm already has https://twitter.com/landley/status/1062570074752589824 ) So
> "build from source in a genericish way" is worth extra cycles from me when it's
> low hanging fruit...
>
> I'm told the mac mini is back. Alas their cheapest/crappiest one is $800 so I'm
> not likely to get it. But as an ssh-able test machine, there should be one in a
> lab somewhere? (How do you regression test the mac build now?)

we don't have automated testing for macOS. most engineers don't have a
mac, and the continuous build infrastructure doesn't build for the
mac. (the _NDK_ continuous build does. that actually matters --- most
NDK users use Windows, but most of the rest use macOS rather than
Linux.)

basically we submit changes, and then the next day or so -- depending
on how broken the mac build already is -- we might get a mail telling
us we've broken the mac build. the mac build is usually broken.

so, yeah, you'll get no good answer to this question from me :-)

what i'm doing right now is hacking about on a loaner macbook that
i'll have to give back soon. if maintaining toybox for mac becomes
important enough, i can just give in and get a mac in addition to my
big boy linux laptop.

> Rob