From owner-freebsd-current Wed Dec 9 17:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28774 for freebsd-current-outgoing; Wed, 9 Dec 1998 17:22:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28769 for ; Wed, 9 Dec 1998 17:22:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id RAA27790; Wed, 9 Dec 1998 17:22:12 -0800 (PST) To: Christopher Masto cc: John Polstra , current@FreeBSD.ORG Subject: Re: buildworld and PAM and login and stuff In-reply-to: Your message of "Wed, 09 Dec 1998 14:56:57 EST." <19981209145657.B14732@netmonger.net> Date: Wed, 09 Dec 1998 17:22:12 -0800 Message-ID: <27787.913252932@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If there are nonstandard options that cause the build to fail in the > middle, perhaps they should be documented or even detected. I believe How? There is a huge array of possible ways in which to hang yourself here and I'm almost certain it would be impossible to enumerate, let along detect, them all. How do you detect that someone has passed in bogus CFLAGS, for example? Or set the optimization too high? All of those things can cause the build to fail and are only examples of some of the less subtle ways of doing it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message