From owner-freebsd-current@FreeBSD.ORG Tue Jan 15 23:44:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C1785941; Tue, 15 Jan 2013 23:44:43 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 98E3B353; Tue, 15 Jan 2013 23:44:43 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id EC6FA23F763; Tue, 15 Jan 2013 18:44:41 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.7.1 onyx.glenbarber.us EC6FA23F763 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none (insecure policy) Date: Tue, 15 Jan 2013 18:44:39 -0500 From: Glen Barber To: Steve Kargl Subject: Re: Missing compile_et and kerberos breaks buildworld Message-ID: <20130115234439.GA1313@glenbarber.us> References: <20130115233525.GA18192@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: <20130115233525.GA18192@troutmask.apl.washington.edu> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2013 23:44:43 -0000 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 15, 2013 at 03:35:25PM -0800, Steve Kargl wrote: > It seems that buildworld depends on the existence of > /usr/bin/compile_et if one wants to build WITH_KERBEROS > on a system that has never had Kerberos support. I > discovered this issue when des@ removed the NOFOO and > NO_FOO options, and the NO_KERBEROS=3D"YES" in my > /etc/make.conf was neutered. The system in question > has never had kerneros installed. One can emulate > the problem as follows: >=20 For what it is worth, reverting the removal of NO_FOO, et. al, will not fix your issue. I ran into this several months ago, and found out "the hard way" that many of our ports require kerberos, even if they do not advertise it - so building without kerberos on the system would fail. I started digging into it, and found what you found - compile_et does not get built prior to building the kerberos bits. It actually gets quite worse from there. I do not recall the details off-hand, but I recall doing 'make obj all install' in somewhat this order: - secure/ - include/ - kerberos5/ [some steps may be missing] Once I had compile_et, install_et, and a few things I do not recall right now, I could then go through and do a full buildworld/installworld. I never got much further in tracking this down. :( Glen --J/dobhs11T7y2rNN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQ9ennAAoJEFJPDDeguUajda0H/jQsKvifW5rFIPa1b0U8Nb6s mMEcALOql0xXXtK56BcVbt89ntLjrDNYsLqpG5xQLzqu0InuUvEMDRtx23N5P+HC jQF3Pj9gIFIxdSRMc0fifDme0+j0eNZ6DFJIvF0uVwaNrWf9ftOfDam+ZYS0DEny tZS4H9wCVPX0VGcTsE5hdHMgJ4dPDKhwqPY09nNuVICjUVwps/ivsC7dYs8rnX3C zndynOLThJlgTGsBIiH4aiRJaZlWGG12Ex8dNw4Q0kjkWqjn94nIBDGBWE6LpKrP JIN/4zaKWAg424r0M3vC4OSA6dk/nTrQCz2llK/AitwRoUwRK4m+4YGqcz5vM1Y= =OEvk -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN--