X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C81689.367E6C8F@onstor-exch02.onstor.net>; Wed, 24 Oct 2007 13:59:56 -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: This AM's Kernel build error
Date: Wed, 24 Oct 2007 13:59:56 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E056C9160@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E02F3DA2A@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: This AM's Kernel build error
Thread-Index: AcgWf3tga1yYOkj9SO69Vho04mV1CAAAEVS6AAAY23AAAZY2RAAAGmGQ
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

Hi Ken,
   Andy suggested that instead of checking for PROD being bc or ch and
not running the Kernel build just setting PROD=3Dbl and running the =
kernel
build for bobcat Linux.

Given that I already have a target that does that, kernel-bl, I am going
to change the kernel target to be just:

kernel: kernel-bl

Because of this change I suggest you change your script to make
kernel-bl and kernel-cg versus just kernel.

Example:
make VARIANT=3Ddbg DESTDIR=3D/var/nfsroot/bobcat =
TFTPDIR=3D/var/nfsroot/bobcat
kernel-bl 2>&1 |tee ${BUILDLOGS}/linux-kernel-bl-dbg.log

make VARIANT=3Ddbg DESTDIR=3D/var/nfsroot/cougar =
TFTPDIR=3D/var/nfsroot/cougar
kernel-cg 2>&1 |tee ${BUILDLOGS}/linux-kernel-cg-dbg.log

-----Original Message-----
From: Ken Renshaw=20
Sent: Wednesday, October 24, 2007 2:40 PM
To: Larry Scheer; Andy Sharp
Subject: RE: This AM's Kernel build error

Here's what I've got now for the kernel build variants, bl and cg for
both opt and dbg:

>               # Build the linux kernel variants
>
>               echo "" >> ${BUILDLOGS}/auditlog
>                 echo "***** Compilation of linux kernel variants
beginning at `date`" >> ${BUILDLOGS}/auditlog
>
>               cd ..
>
>               if [ ${OK2DEBUG} =3D=3D "true" ]; then
>
>                       make VARIANT=3Ddbg PROD=3Dbl
DESTDIR=3D/var/nfsroot/bobcat TFTPDIR=3D/var/nfsroot/bobcat kernel\
>                               2>&1 |tee
${BUILDLOGS}/linux-kernel-bl-dbg.log
>                       make VARIANT=3Ddbg PROD=3Dcg
DESTDIR=3D/var/nfsroot/cougar TFTPDIR=3D/var/nfsroot/cougar kernel\
>                               2>&1 |tee
${BUILDLOGS}/linux-kernel-cg-dbg.log
>
>               fi
>
>               make VARIANT=3Dopt PROD=3Dbl =
DESTDIR=3D/var/nfsroot/bobcat
TFTPDIR=3D/var/nfsroot/bobcat kernel\
>                       2>&1 |tee ${BUILDLOGS}/linux-kernel-bl-opt.log
>               make VARIANT=3Dopt PROD=3Dcg =
DESTDIR=3D/var/nfsroot/cougar
TFTPDIR=3D/var/nfsroot/cougar kernel\
>                       2>&1 |tee ${BUILDLOGS}/linux-kernel-cg-opt.log

Thanks,

-Ken


-----Original Message-----
From: Larry Scheer
Sent: Wed 10/24/2007 2:20 PM
To: Ken Renshaw; Andy Sharp
Subject: RE: This AM's Kernel build error
=20
The top level Kernel target now needs some command line variables. Since
we will soon be building both bobcat and cougar Linux kernels a PROD
variable is needed. Since we will also be building for both NFS root
filesystems and a compact flash filesystem two more variables are
needed, DESTDIR and TFTPDIR. Since you need so many command line
variables might as well throw in VARIANT. It, too, is needed.

I am planning on creating the make release targets to set these for you
but until I get that together this is how you should invoke the kernel
build.

cd .. && make VARIANT=3Ddbg (or opt) PROD=3Dbl (or cg)
DESTDIR=3D/var/nfsroot/bobcat TFTPDIR=3D/var/nfsroot/bobcat

For PROD=3Dcg use /var/nfsroot/cougar for DESTDIR and TFTPDIR.

Of course if you have a bobcat Linux box then you want to set TFTPDIR to
the actual directory your bobcat boots from. Since you don't have one of
these setting DESTDIR and TFTPDIR to the same directory is good enough
for the time being.

I will also change the top level Makefile so if PROD=3Dch or bc the =
Linux
kernel target won't fire.

Larry

-----Original Message-----
From: Ken Renshaw=20
Sent: Wednesday, October 24, 2007 1:52 PM
To: Andy Sharp; Larry Scheer
Subject: RE: This AM's Kernel build error

Hi guys. This is what I'm doing:

#
# Cougar and Bobcat Linux targets, compile only
#

        if [ ${NIGHTLY} =3D=3D "true" ]; then

                # First build the linux kernel...

                echo "" >> ${BUILDLOGS}/auditlog
                echo "***** bc and ch target builds completed,
compilation of linux kernel beginning at `date`" >>
${BUILDLOGS}/auditlog
                cd .. && make kernel 2>&1 |tee
${BUILDLOGS}/linux-kernel-compile.log
                cd nfx-tree
                echo "" >> ${BUILDLOGS}/auditlog
                echo "***** Compilation of linux kernel completed, cg
and bl target builds now starting at `date`" >> ${BUILDLOGS}/auditlog

                # ..and then the cougar and bobcat-on-linux targets.
                make ${MKFLAGS} VARIANT=3Ddbg PROD=3Dcg all 2>&1 |tee
${BUILDLOGS}/cg-dbg-compile.log
                make ${MKFLAGS} VARIANT=3Dopt PROD=3Dcg all 2>&1 |tee
${BUILDLOGS}/cg-opt-compile.log
                make ${MKFLAGS} VARIANT=3Ddbg PROD=3Dbl all 2>&1 |tee
${BUILDLOGS}/bl-dbg-compile.log
                make ${MKFLAGS} VARIANT=3Dopt PROD=3Dbl all 2>&1 |tee
${BUILDLOGS}/bl-opt-compile.log
                echo "" >> ${BUILDLOGS}/auditlog
                echo "***** Compilation of cg and bl target builds
completed at `date`" >> ${BUILDLOGS}/auditlog

        fi


it would be nice if the makefile disallowed building on cheetah, but
I'll go ahead and change the build script to skip building linux for
cheetah.

Thanks,

-Ken


-----Original Message-----
From: Andy Sharp
Sent: Wed 10/24/2007 1:50 PM
To: Larry Scheer
Cc: Ken Renshaw
Subject: Re: This AM's Kernel build error
=20
The makefile should prevent this, unless someone is doing something
strange.

On Wed, 24 Oct 2007 13:26:02 -0700 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> Looks like the kernel build failed because PROD was set to "ch"
> (cheetah)
>=20
> make -C linux/rootfs DESTDIR=3D/perforce/trees/dev/distr TFTPDIR=3D
> PROD=3Dch kernel
> ...
> ...
> ...
> make[3]: Leaving directory
> `/perforce/trees/dev/linux/kernel/linux-mips-2.6'
> /usr/local/sde4/bin/conv -f bin -o linux-mips-2.6/vmlinux.bin
> a.out: No such file or directory
> make[2]: *** [linux-mips-2.6/vmlinux.bin] Error 1
> make[2]: Leaving directory `/perforce/trees/dev/linux/kernel'
> make[1]: *** [/perforce/trees/dev/distr/boot/vmlinux.bin] Error 2
> make[1]: Leaving directory `/perforce/trees/dev/linux/rootfs'
> make: *** [kernel] Error 2
>=20
>=20
> Ken,=20
>     How does your build script invoke the linux kernel build?
>=20
>=20
> Larry


