From owner-cvs-src@FreeBSD.ORG  Wed Apr 30 10:15:07 2003
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id BEFEA37B4E8; Wed, 30 Apr 2003 10:15:07 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 6EABF43FAF; Wed, 30 Apr 2003 10:15:06 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h3UHF3Nj027457;
	Wed, 30 Apr 2003 19:15:03 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: "Kenneth D. Merry" <ken@kdm.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Wed, 30 Apr 2003 10:12:40 MDT."
             <20030430101240.A3295@panzer.kdm.org> 
Date: Wed, 30 Apr 2003 19:15:03 +0200
Message-ID: <27456.1051722903@critter.freebsd.dk>
cc: cvs-src@FreeBSD.org
cc: src-committers@FreeBSD.org
cc: cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/sys/cam/scsi scsi_da.c 
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2003 17:15:08 -0000

In message <20030430101240.A3295@panzer.kdm.org>, "Kenneth D. Merry" writes:

>> Actually, that's interesting.  I seem to have caught it in my private
>> extension of universe:  I build a native and a sparc64 cross release.
>> 
>> I'm sure there is a good explanation why it breaks the kernel in the
>> cross-release but not in the cross-world...
>
>It does break the kernel builds, it's just that you have to dig through the
>logs for each kernel build to see the breakage.  It doesn't show up in the
>top level make universe output.

Hmm, that is a bug in our Makefiles then, buildkernel should explode
if it fails...


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.