From owner-freebsd-current Tue Oct 29 8: 3:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DED0937B401 for ; Tue, 29 Oct 2002 08:03:11 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5868543E7B for ; Tue, 29 Oct 2002 08:03:09 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id g9TG2xrF092882; Tue, 29 Oct 2002 17:02:59 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dag-Erling Smorgrav Cc: current@freebsd.org Subject: Re: The next "make release" breaker... In-Reply-To: Your message of "Tue, 29 Oct 2002 16:25:56 +0100." Date: Tue, 29 Oct 2002 17:02:59 +0100 Message-ID: <92881.1035907379@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Dag-Erling Smorgrav writes: >Poul-Henning Kamp writes: >> Inside the chroot. > >'make release' checks out src in the sandbox, then chroots to it and >does a plain 'make world' right? There's no chance the sources in the >sandbox were stale, or it was trying to do something fancy? What >about the sandbox itself - what sources was it built from? Does 'nm >${chroot}/usr/lib/libssh.so' show mm_auth_krb5? (though the build >should succeed even if the sandbox contains a stale libssh) > >> I'll upload the log file if it breaks again. > >Please do, because this is really weird. http://phk.freebsd.dk/misc/_.release I think it is related to all the crypto magic in make release... -- 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message