X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B9AF.222AA360@onstor-exch02.onstor.net>; Thu, 28 Jun 2007 10:07:04 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B9AF.222AA360"
References: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D388@onstor-exch02.onstor.net> <20070628104956.6b67209a@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: cougar builds
Date: Thu, 28 Jun 2007 10:02:15 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D38D@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: cougar builds
Thread-Index: Ace5rL1fMqw+rSDNR8eOR4zGCPnMFQAAbhPn
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_01C7B9AF.222AA360
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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


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

</BODY>
</HTML>
------_=_NextPart_001_01C7B9AF.222AA360--
