Re: Keeping up to date with -current with a cross-compiler

[David Riley <fraveydank%gmail.com@localhost>]

On Dec 12, 2011, at 6:46 PM, John Klos wrote:

>> I definitely did this successfully a few months ago, but the knowledge seems 
>> to have leaked out of my brain since then.  I'm crosscompiling -current on 
>> OS X (because I can actually do the CVS update and build the entire 
>> distribution in less time than the 9500 takes to do the CVS update).
> 
> Damn... that's either a fast OS X machine or a slow 9500...

I've noticed that the 9500 is pretty slow on modern NetBSD, especially compared 
to the speed I remember from the 1.6 days.  I don't remember if that's 
nostalgia covering my memory or not, but disk I/O seems particularly slow (I'm 
using MESH).  I'd run a profiling build, but that seems to have trouble with 
build.sh (and the patch I saw online a year or so ago to add that to build.sh 
never seems to have made it into the mainline).

It's also a fairly speedy OS X machine. :-)  You can put a lot of compute power 
into an iMac these days...

>> What's the optimum way of transferring the userland over?  NFS?  Tar it up 
>> and extract?  I'd rather not use sysinst (this box runs headless most of the 
>> time and it's a hassle doing anything other than ssh, but it can be done if 
>> need be).
> 
> Use build.sh to make sets (sets is a target) after making distribution, then 
> scp the .tgz files over. Don't untargzip etc.tgz, just the others. Then run 
> postinstall and point it to etc.tgz.

Roger that, makes sense.  Didn't make sense to build a whole release, but I 
didn't know about the sets option (I guess I didn't RTFM as much as I thought I 
did).

Thanks!


- Dave