X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B9B3.8D7893B8@onstor-exch02.onstor.net>; Thu, 28 Jun 2007 10:38:42 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: cougar builds
Date: Thu, 28 Jun 2007 10:38:42 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02215899@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D38D@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: cougar builds
Thread-Index: Ace5rL1fMqw+rSDNR8eOR4zGCPnMFQAAbhPnAAE4tqA=
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>
Cc: "Jeff Miller" <jeff.miller@onstor.com>

That selecttz problem rings a bell... Isn't that the error you get when
you try to do  a make release a second time before a make release-clean
was run?

L.

-----Original Message-----
From: Ken Renshaw=20
Sent: Thursday, June 28, 2007 11:02 AM
To: Andy Sharp
Cc: Jeff Miller; Larry Scheer
Subject: RE: cougar builds

I'm assuming my openbsd build is fine, things are built and the logs
don't document explosions at any rate. All EverON targets are building,
the only thing that is failing is the packaging, with this error:

<snippet of make release>
/usr/bin/sudo mv -f bin ../../../../bin.unstripped &&\
/usr/bin/sudo mkdir -p bin &&\
/usr/bin/sudo chmod 777 bin &&\
cd ../../../../bin.unstripped &&\
/usr/bin/sudo mv -f selecttz ../Release/usr/local/agile/bin &&\
/usr/bin/sudo mv -f verify_install.sh ../Release/usr/local/agile/bin &&\
/perforce/trees/cougar/nfx-tree/extra/strip.sh
mv: cannot stat `selecttz': No such file or directory

The file selecttz is getting built:

[build@k2 nfx-tree]$ sudo find . -name selecttz
./code/ssc-nfxsh/selecttz
[build@k2 nfx-tree]$ sudo find . -name verify_install.sh
./code/ssc-nfxsh/verify_install.sh
[build@k2 nfx-tree]$ ls -l ./code/ssc-nfxsh/selecttz
-r-xr-xr-x    1 build    build         633 Jun 27 21:57
./code/ssc-nfxsh/selecttz


I'll track it down guys, thanks for confirming that the process should
be the same.

Have a good one.

-Ken=20

-----Original Message-----
From: Andy Sharp
Sent: Thu 6/28/2007 10:49 AM
To: Ken Renshaw
Cc: Jeff Miller; Larry Scheer
Subject: Re: cougar builds
=20
On Thu, 28 Jun 2007 10:41:15 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> Hi Jeff. I setup and did a couple trial runs for the cougar nightly
> build process yesterday, and I have a question or two. First, is
> there anything different in compiling OpenBSD these days? Like
> setting SSC for cheetah being a requirement, if so to what, etc.
> Basically I expect these targets to work, or variations of them:
>=20
> checkout clean sources ( w/ modtime set in p4 client so as not to
> retrigger configure ) make bsd-cross-base ( w/ nomodtime set in p4
> client ) make bsd-build-all ( used to build cheetah kernel as default
> SSC ) make SSC=3DBOBCAT bsd-kernel-config bsd-kernel

If this does not work, then we need to fix it, because whatever you
were doing before cougar should work with the same expected results.
What I didn't hear is whether or not this worked.

> If someone could let me know what I need to accommodate for cougar
> tree builds I'd appreciate it. The plan is to build all variants on
> all platforms, scan for errors and warnings, etc., but until such
> time as cougar hardware exists I can only use cheetah opt/dbg to run
> autoregressions on. Perhaps a little later I can get a bobcat to
> start bl verification ( and linux verification in general ).
>=20
> Thanks,
>=20
> -Ken
>=20

