Re: rust and rust-bin confusion

[Greg Troxel <gdt%lexort.com@localhost>]

John Klos <john%klos.com@localhost> writes:

> I have an earmv6h system on which I want to be able to run a browser
> if needed, if just to get past the captive portals on wifi networks
> that have them, but rust isn't going to build on a system with 512
> megs.
>
> I set up an older 1200 MHz Raspberry Pi 3 with a USB SSD, an earmv6hf
> kernel and userland, and 4 gigs of swap. Aside from "gpu_mem=16" in
> /boot/config.txt and stopping all the daemons that aren't needed
> (cron, syslogd, inetd, postfix, dhcpcd, et cetera), I just "unlimit"
> and "make package" in /usr/pkgsrc/lang/rust.
>
> This last time I saw multiple rust running at the same time in spite
> of "MAKE_JOBS=1", so I interrupted the build and tried cpuctl offline
> for three of the cores, but that didn't change anything, so I then
> explicitly replaced ${_MAKE_JOBS_N} with 1 in Makefile because I
> didn't know (and still don't know) what actually works to tell rust to
> not assume the whole system belongs to it.
>
> I considered compiling a uniprocessor kernel, but the build succeeded
> after changing Makefile. Go figure.

Even with that degree of handholding it is indeed news that it builds.
It seems like our current rust can build in less memory than some
previous versions.

That is quite a ways from "I just typed make package and it worked, and
I'd expect it to work for random others", so I don't think it argues
against the default change.  I think bulk builds will still attempt both
lang/rust and lang/rust-bin.

(Sounds like there is a bug with MAKE_JOBS to be fixed.)

I am guessing gpu_mem=16 is to reduce the RAM allocation for video to
get more for building?  It would be nice if that were in the RPI howto.