X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B9AC.AB2ED336@onstor-exch02.onstor.net>; Thu, 28 Jun 2007 09:49:26 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B9AC.AB2ED336"
References: <BB375AF679D4A34E9CA8DFA650E2B04E018A69AE@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: cougar builds
Date: Thu, 28 Jun 2007 09:47:08 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D38B@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: cougar builds
Thread-Index: Ace5q4bTJc1D1co9RxeMm99Xeq+RGAAAEoOgAAAiEWw=
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Jeff Miller" <jeff.miller@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

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

My questions are specifically regarding the 'rest' of the product, i.e. =
the OS. I'm running into a make release packaging issue with the =
bsd-distr subtarget, and in the process of looking at changes that were =
done to //depot/cougar/openbsd/... I saw a couple things like cougar =
kernel being the default instead of cheetah now, so I wanted to check =
with the dev team before I continue triaging my packaging issues.

Thanks,

-Ken


-----Original Message-----
From: Jeff Miller
Sent: Thu 6/28/2007 10:46 AM
To: Ken Renshaw
Cc: Larry Scheer; Andy Sharp
Subject: RE: cougar builds
=20
Ken,
Does something not work?  I have been building all 8 variants from =
nfx-tree. I have not been building BSD or Linux.
Jeff

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

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:

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 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 ).

Thanks,

-Ken



------_=_NextPart_001_01C7B9AC.AB2ED336
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>My questions are specifically regarding the 'rest' of =
the product, i.e. the OS. I'm running into a make release packaging =
issue with the bsd-distr subtarget, and in the process of looking at =
changes that were done to //depot/cougar/openbsd/... I saw a couple =
things like cougar kernel being the default instead of cheetah now, so I =
wanted to check with the dev team before I continue triaging my =
packaging issues.<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Jeff Miller<BR>
Sent: Thu 6/28/2007 10:46 AM<BR>
To: Ken Renshaw<BR>
Cc: Larry Scheer; Andy Sharp<BR>
Subject: RE: cougar builds<BR>
<BR>
Ken,<BR>
Does something not work?&nbsp; I have been building all 8 variants from =
nfx-tree. I have not been building BSD or Linux.<BR>
Jeff<BR>
<BR>
-----Original Message-----<BR>
From: Ken Renshaw<BR>
Sent: Thursday, June 28, 2007 10:41 AM<BR>
To: Jeff Miller<BR>
Cc: Larry Scheer; Andy Sharp<BR>
Subject: cougar builds<BR>
<BR>
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:<BR>
<BR>
checkout clean sources ( w/ modtime set in p4 client so as not to =
retrigger configure )<BR>
make bsd-cross-base ( w/ nomodtime set in p4 client )<BR>
make bsd-build-all ( used to build cheetah kernel as default SSC )<BR>
make SSC=3DBOBCAT bsd-kernel-config bsd-kernel<BR>
<BR>
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 ).<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7B9AC.AB2ED336--
