Date: Thu, 25 Jul 2002 09:21:46 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: current@freebsd.org Cc: des@ofug.org Subject: Re: sparc64 tinderbox failure Message-ID: <200207251621.g6PGLkBg033883@vashon.polstra.com> In-Reply-To: <xzp3cu7ok71.fsf@flood.ping.uio.no> References: <200207241200.g6OC0dJJ005500@bowie.private> <20020724101904.D201@espresso.q9media.com> <200207241542.g6OFgC9b032281@vashon.polstra.com> <xzp3cu7ok71.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <xzp3cu7ok71.fsf@flood.ping.uio.no>,
Dag-Erling Smorgrav <des@ofug.org> wrote:
> John Polstra <jdp@polstra.com> writes:
> > Does tinderbox run with a nonstandard WARNS setting? I did the
> > cross build with these environment settings:
>
> des@freefall ~% cat tinderbox/make.conf
> CFLAGS = -O -pipe
> COPTFLAGS = -O -pipe
> NOPROFILE = true
> MAKE_KERBEROS4 = yes
> MAKE_KERBEROS5 = yes
>
> and the relevant bits of tinderbox.sh:
>
> /bin/mkdir -p "${obj}"
> MAKEOBJDIRPREFIX="${obj}"; export MAKEOBJDIRPREFIX
> __MAKE_CONF="${base}/make.conf"; export __MAKE_CONF
> /usr/bin/make -s buildworld
> for kc in ${kernels} ; do
> (cd sys/${arch}/conf && make ${kc})
> /usr/bin/make -s buildkernel KERNCONF=${kc} -DNO_WERROR
> done
Now I'm really confused. If the script is passing -DNO_WERROR to
the buildkernel invocation then why did a warning kill the build?
John
--
John Polstra
John D. Polstra & Co., Inc. Seattle, Washington USA
"Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207251621.g6PGLkBg033883>