X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B9B0.91715DBE@onstor-exch02.onstor.net>; Thu, 28 Jun 2007 10:17:20 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B9B0.91715DBE"
References: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D388@onstor-exch02.onstor.net><20070628104956.6b67209a@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02F3D38D@onstor-exch02.onstor.net> <20070628111305.4fd7e336@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: cougar builds
Date: Thu, 28 Jun 2007 10:15:41 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D38E@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: cougar builds
Thread-Index: Ace5r/lmSfwpQxzLTyi+DtnWdWxVMQAAFytn
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Jeff Miller" <jeff.miller@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B9B0.91715DBE
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

No big rush. I'll definitely wait to hear from Larry if this is =
something he's seeing or not, and if it's a global issue then by all =
means he can fix it.

Thanks,

-Ken


-----Original Message-----
From: Andy Sharp
Sent: Thu 6/28/2007 11:13 AM
To: Ken Renshaw
Cc: Jeff Miller; Larry Scheer
Subject: Re: cougar builds
=20
Unless you really have a hankerin' to do it, you should leave this to
Larry.

On Thu, 28 Jun 2007 11:02:15 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> 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:
>=20
> <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
>=20
> The file selecttz is getting built:
>=20
> [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
>=20
>=20
> I'll track it down guys, thanks for confirming that the process
> should be the same.
>=20
> Have a good one.
>=20
> -Ken=20
>=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:
>=20
> > 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
>=20
> 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.
>=20
> > 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
>=20


------_=_NextPart_001_01C7B9B0.91715DBE
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: cougar builds</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>No big rush. I'll definitely wait to hear from Larry =
if this is something he's seeing or not, and if it's a global issue then =
by all means he can fix it.<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Andy Sharp<BR>
Sent: Thu 6/28/2007 11:13 AM<BR>
To: Ken Renshaw<BR>
Cc: Jeff Miller; Larry Scheer<BR>
Subject: Re: cougar builds<BR>
<BR>
Unless you really have a hankerin' to do it, you should leave this =
to<BR>
Larry.<BR>
<BR>
On Thu, 28 Jun 2007 11:02:15 -0700 &quot;Ken Renshaw&quot;<BR>
&lt;ken.renshaw@onstor.com&gt; wrote:<BR>
<BR>
&gt; I'm assuming my openbsd build is fine, things are built and the =
logs<BR>
&gt; don't document explosions at any rate. All EverON targets are<BR>
&gt; building, the only thing that is failing is the packaging, with =
this<BR>
&gt; error:<BR>
&gt;<BR>
&gt; &lt;snippet of make release&gt;<BR>
&gt; /usr/bin/sudo mv -f bin ../../../../bin.unstripped &amp;&amp;\<BR>
&gt; /usr/bin/sudo mkdir -p bin &amp;&amp;\<BR>
&gt; /usr/bin/sudo chmod 777 bin &amp;&amp;\<BR>
&gt; cd ../../../../bin.unstripped &amp;&amp;\<BR>
&gt; /usr/bin/sudo mv -f selecttz ../Release/usr/local/agile/bin =
&amp;&amp;\<BR>
&gt; /usr/bin/sudo mv -f verify_install.sh =
../Release/usr/local/agile/bin<BR>
&gt; &amp;&amp;\ /perforce/trees/cougar/nfx-tree/extra/strip.sh<BR>
&gt; mv: cannot stat `selecttz': No such file or directory<BR>
&gt;<BR>
&gt; The file selecttz is getting built:<BR>
&gt;<BR>
&gt; [build@k2 nfx-tree]$ sudo find . -name selecttz<BR>
&gt; ./code/ssc-nfxsh/selecttz<BR>
&gt; [build@k2 nfx-tree]$ sudo find . -name verify_install.sh<BR>
&gt; ./code/ssc-nfxsh/verify_install.sh<BR>
&gt; [build@k2 nfx-tree]$ ls -l ./code/ssc-nfxsh/selecttz<BR>
&gt; -r-xr-xr-x&nbsp;&nbsp;&nbsp; 1 build&nbsp;&nbsp;&nbsp; =
build&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 633 Jun 27<BR>
&gt; 21:57 ./code/ssc-nfxsh/selecttz<BR>
&gt;<BR>
&gt;<BR>
&gt; I'll track it down guys, thanks for confirming that the process<BR>
&gt; should be the same.<BR>
&gt;<BR>
&gt; Have a good one.<BR>
&gt;<BR>
&gt; -Ken<BR>
&gt;<BR>
&gt; -----Original Message-----<BR>
&gt; From: Andy Sharp<BR>
&gt; Sent: Thu 6/28/2007 10:49 AM<BR>
&gt; To: Ken Renshaw<BR>
&gt; Cc: Jeff Miller; Larry Scheer<BR>
&gt; Subject: Re: cougar builds<BR>
&gt;&nbsp;<BR>
&gt; On Thu, 28 Jun 2007 10:41:15 -0700 &quot;Ken Renshaw&quot;<BR>
&gt; &lt;ken.renshaw@onstor.com&gt; wrote:<BR>
&gt;<BR>
&gt; &gt; Hi Jeff. I setup and did a couple trial runs for the cougar =
nightly<BR>
&gt; &gt; build process yesterday, and I have a question or two. First, =
is<BR>
&gt; &gt; there anything different in compiling OpenBSD these days? =
Like<BR>
&gt; &gt; setting SSC for cheetah being a requirement, if so to what, =
etc.<BR>
&gt; &gt; Basically I expect these targets to work, or variations of =
them:<BR>
&gt; &gt;<BR>
&gt; &gt; checkout clean sources ( w/ modtime set in p4 client so as not =
to<BR>
&gt; &gt; retrigger configure ) make bsd-cross-base ( w/ nomodtime set =
in p4<BR>
&gt; &gt; client ) make bsd-build-all ( used to build cheetah kernel =
as<BR>
&gt; &gt; default SSC ) make SSC=3DBOBCAT bsd-kernel-config =
bsd-kernel<BR>
&gt;<BR>
&gt; If this does not work, then we need to fix it, because whatever =
you<BR>
&gt; were doing before cougar should work with the same expected =
results.<BR>
&gt; What I didn't hear is whether or not this worked.<BR>
&gt;<BR>
&gt; &gt; If someone could let me know what I need to accommodate for =
cougar<BR>
&gt; &gt; tree builds I'd appreciate it. The plan is to build all =
variants on<BR>
&gt; &gt; all platforms, scan for errors and warnings, etc., but until =
such<BR>
&gt; &gt; time as cougar hardware exists I can only use cheetah opt/dbg =
to run<BR>
&gt; &gt; autoregressions on. Perhaps a little later I can get a bobcat =
to<BR>
&gt; &gt; start bl verification ( and linux verification in general =
).<BR>
&gt; &gt;<BR>
&gt; &gt; Thanks,<BR>
&gt; &gt;<BR>
&gt; &gt; -Ken<BR>
&gt; &gt;<BR>
&gt;<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7B9B0.91715DBE--
