AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090709093202.48a703df@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:mail.onstor.net
NSV:
SSH:
R:<larry.scheer@onstor.com>,<Arnaldo.Roldan@onstor.com>,<Ron.Whitham@onstor.com>,<maxim.kozlovsky@onstor.com>,<brian.stark@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	102AB4F33EBBDB4C91915B145C8E9FB31377A3D4D4@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 9 Jul 2009 09:32:15 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Larry Scheer <larry.scheer@onstor.com>
Cc: Arnaldo Roldan <Arnaldo.Roldan@onstor.com>, Ron Whitham
 <Ron.Whitham@onstor.com>, Maxim Kozlovsky <maxim.kozlovsky@onstor.com>,
 Brian Stark <brian.stark@onstor.com>
Subject: Re: engineering workstation
Message-ID: <20090709093215.21c4e27a@ripper.onstor.net>
In-Reply-To: <102AB4F33EBBDB4C91915B145C8E9FB31377A3D4D4@exch1.onstor.net>
References: <20090708190918.3c145d8c@ripper.onstor.net>
	<102AB4F33EBBDB4C91915B145C8E9FB31377A3D4D4@exch1.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 9 Jul 2009 09:05:45 -0700 Larry Scheer
<larry.scheer@onstor.com> wrote:

> The freebsd-utils package has tons of dependencies that load all
> kinds of redundant crap of questionable value onto the workstation. I
> don't think it is worth the hassle just to get bsdmake.

I must be missing something.  I show it only depends on dash.  Were you
looking at freebsd5-buildutils?  Anyway, it doesn't matter....

> We do have the source to build bsdmake and the other BSD build
> utilities in openbsd/src. That piece is safe to build. It doesn't
> attempt to install the utilities in system directories.

Yes, I know we have the source, but don't they use makefiles written
for bsdmake?

> Does anyone else agree with Andy that we don't need to build bobcat
> code on this new workstation? (I am not talking about building
> openbsd/src just being able to do a make release for bobcat.)

Oooooooooh, they'd better.  Of course, if someone _really_ wanted to
build bobcat on their workstation, we could just put a chroot on their
system and they can build inside of that.

I say we declare victory and move forward.

> Larry
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Wednesday, July 08, 2009 7:09 PM
> To: Larry Scheer
> Cc: Arnaldo Roldan; Ron Whitham; Maxim Kozlovsky; Brian Stark
> Subject: Re: engineering workstation
> 
> On Wed, 8 Jul 2009 18:48:42 -0700 Larry Scheer
> <larry.scheer@onstor.com> wrote:
> 
> > Everyone,
> >    I just wanted to give you a progress update on the engineering
> > workstation.
> > 
> > I have all the packages installed and make install_toolchain works
> > on Debian systems. I am waiting for Andy to review my changes and I
> > will check in code and packages.
> > 
> > I was able to successfully build the cougar product (make
> > PROD=cg ... and make release PROD=cg ...) 
> > 
> > I was able to build the nfx-tree for bobcat but a make release
> > PROD=bc fails. There seem to be problems with running the bsdmake
> > found in boot-tools with this hardware and Debian release. I am
> > attempting to rebuild bsdmake and boot-tools for this platform but I
> > ran into compile errors.
> 
> I don't think bobcat builds are a priority for this workstation: they
> can still be done on build servers if necessary.  Like I mentioned in
> the past, trying to build BSD on my debian box led to serious
> headaches, including our build process overwriting /usr/include.
> 
> You can find a suitable bsd make in the freebsd-buildutils package.
> Not sure how you would do it without that as I don't think there's a
> "make" bootstrap process when building our BSD.  Or any BSD.
> 
> > I will keep plugging away at this to see if I can get the bobcat
> > make release to work. I won't attempt to get a build of OpenBSD to
> > work. There are too many issues to bother trying that. Besides we
> > have several systems that can build it successfully.
> > 
> > I just thought you would like a progress report.
> > 
> > Once I get the bobcat build to complete the next step would be
> > having Jan or someone verify the automated test tools work. Which
> > reminds me, I need to build an amd64 version of the tap library
> > package and install it on engtest0.
> > 
> > Larry
> > 
> > -----Original Message-----
> > From: Arnaldo Roldan 
> > Sent: Tuesday, June 30, 2009 4:59 PM
> > To: Ron Whitham; Andy Sharp
> > Cc: Larry Scheer; Maxim Kozlovsky
> > Subject: RE: engineering workstation
> > 
> > Larry,
> > 
> > We await your prognosis. Thanks,
> > 
> > Arnaldo
> > 
> > -----Original Message-----
> > From: Ron Whitham 
> > Sent: Tuesday, June 30, 2009 12:34 PM
> > To: Andy Sharp; Arnaldo Roldan
> > Cc: Larry Scheer; Maxim Kozlovsky
> > Subject: RE: engineering workstation
> > 
> > engtest0 has been reinstalled with an amd64 build. 
> > same login info as before: 
> > ssh://10.0.0.61
> > root // onstor
> > 
> >  
> > 
> > -----Original Message-----
> > From: Andy Sharp 
> > Sent: Friday, June 26, 2009 6:18 PM
> > To: Arnaldo Roldan
> > Cc: Larry Scheer; Ron Whitham; Maxim Kozlovsky
> > Subject: engineering workstation
> > 
> > Hi folks,
> > 
> > I just noticed that engtest0 is i386, but it needs to be amd64,
> > which is the arch flavor that should be used on all x86_64
> > hardware, either from AMD or Intel.
> > 
> > Not sure why I didn't notice this before, my bad really.  It will
> > have to be reinstalled, sorry.
> > 
> > a
> > 
> > engtest0:~$ dpkg --print-architecture
> > i386
> > engtest0:~$
