From owner-freebsd-arch@FreeBSD.ORG Sat Dec 8 00:16:12 2007 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EE2F16A417 for ; Sat, 8 Dec 2007 00:16:12 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id E7F1713C468 for ; Sat, 8 Dec 2007 00:16:11 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 21828 invoked by uid 399); 7 Dec 2007 23:49:30 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 7 Dec 2007 23:49:30 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <4759DC08.9070600@FreeBSD.org> Date: Fri, 07 Dec 2007 15:49:28 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.9 (X11/20071119) MIME-Version: 1.0 To: freebsd-arch@freebsd.org X-Enigmail-Version: 0.95.5 OpenPGP: id=D5B2F0FB Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig7D950AC219629E304C995BEA" Subject: Should libgssapi be hidden behind the MK_KERBEROS knob? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Dec 2007 00:16:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7D950AC219629E304C995BEA Content-Type: multipart/mixed; boundary="------------040507040604010604050709" This is a multi-part message in MIME format. --------------040507040604010604050709 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If there is a better list for this, don't hesitate to let me know. I use WITHOUT_KERBEROS=3Dtrue in /etc/{make|src}.conf, since I don't need or use it. However, this leads to a problem with building the kdelibs3 port. The configure script looks for the presence of libgssapi and the associated headers, and takes that to mean that kerberos is available, and sets things up accordingly. This causes the build to fail when it tries to actually link something to a kerberos library. I realize that GSS can be used for other things besides kerberos, but are we really losing anything by hiding them both under the same knob? If the answer to that is yes, is there any objection to a WITHOUT_GSS knob? Thanks, Doug --=20 This .signature sanitized for your protection --------------040507040604010604050709 Content-Type: text/plain; name="gss-no-krb.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="gss-no-krb.diff" Index: Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/local/ncvs/src/lib/Makefile,v retrieving revision 1.226 diff -u -r1.226 Makefile --- Makefile 17 Nov 2007 21:29:02 -0000 1.226 +++ Makefile 3 Dec 2007 18:58:08 -0000 @@ -31,7 +31,7 @@ libbegemot ${_libbluetooth} libbsnmp libbz2 \ libcalendar libcam libcompat libdevinfo libdevstat libdisk \ libedit libexpat libfetch libftpio libgeom ${_libgpib} \ - libgssapi libipsec \ + ${_libgssapi} libipsec \ ${_libipx} libkiconv libmagic libmemstat ${_libmilter} ${_libmp} \ ${_libncp} ${_libngatm} libopie libpam libpcap \ libpmc ${_libkse} librt ${_libsdp} ${_libsm} ${_libsmb} \ @@ -120,4 +120,8 @@ _libgpib=3D libgpib .endif =20 +.if ${MK_KERBEROS} !=3D "no" +_libgssapi=3D libgssapi +.endif + --------------040507040604010604050709-- --------------enig7D950AC219629E304C995BEA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (FreeBSD) iD8DBQFHWdwJyIakK9Wy8PsRA9MMAKDI5w0b/8MJbNwrO3htYfaYqfGGTQCdEB8w CvwaGXUvsjU2wcVekVxLF7M= =S0t4 -----END PGP SIGNATURE----- --------------enig7D950AC219629E304C995BEA--