Subject: Re: Building current...
To: Brian Chase <vaxzilla@jarai.org>
From: j wehrli <j@wehrli.org>
List: port-vax
Date: 12/07/2003 15:53:17
Brian Chase wrote:
>On Sun, 7 Dec 2003, der Mouse wrote:
>
>
>
>>>Confirm what? That the VAX-port isn't built natively regularly?
>>>That I can confirm. I usually do builds of -current now and again
>>>(on the 8650), and hits snags that the core group don't notice.
>>>
>>>
>>This is what I was afraid of when the cross-build stuff went in, that
>>NetBSD would end up shipping code with bugs that went unnoticed because
>>they didn't show up in a cross build.
>>
>>
>
>I think we'll be alright as long as we get more VAX people tracking
>and compiling -current. It doesn't require too much in the way of
>resources. I'm managing alright with my 56kb/s dialup and a few GB of
>spare disk space. The bottleneck in the process ends up being VAX cpu
>cycles. :-)
>
>-brian.
>
>
I have extra vaxen currently powered off. I have IDLE; 2 VaxStation
3100/72 32MB MEM and 3 VaxStation 4000/90 32MB MEM.
What should I setup to help? I think they have NetNSD 1.6 on them
currently as I try to track release best I can.
Is 1.6 the right version to set up a native built box that tracks
-current? I have 384/128 DSL with 5 static IPs and a 60GB NetBSD
fileserver that can spare 10 or 20 GB for the VAXEN effort. I would be
willing to buy another if needed and it helps keep NetBSD working on VAX.
I figure I would set up a native build box and then perhaps second box
to boot and run your regression tests. I have little knowledge of the
testing setup NetBSD kernel uses. Please advise on a setup preference. I
prefer to leave only one VAX server on 7/24 since I already have several
PC and servers running and have a small house with 100A power. On the
plus side winter is here and the basement could use the heat :)
I suppose after that I could look into a pkgsrc builder. It seems that
even native binaries for NETBSD releases is lacking let alone for
current packages. Lots of compile cycles for that I am sure. I have
limited skills to diagnose kernel or package problems but I do not mind
donating electric power and vax cycle for NetBSD. I would not mind
allowing NetBSD/Vax folks to SSH in to view/adjust things and perform
regressions.
Let me know how to help.
Cheers
Joe Wehrli