From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 16 01:17:12 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DD22106566C for ; Tue, 16 Nov 2010 01:17:12 +0000 (UTC) (envelope-from ben@b1c1l1.com) Received: from lancer.b1c1l1.com (unknown [IPv6:2607:f358:1a:1a:1000::]) by mx1.freebsd.org (Postfix) with ESMTP id 555A48FC18 for ; Tue, 16 Nov 2010 01:17:12 +0000 (UTC) Received: from supra.b1c1l1.com (unknown [IPv6:2607:fc48:12:2:225:4bff:fecf:472e]) by lancer.b1c1l1.com (Postfix) with ESMTPSA id EC0BE5C34; Mon, 15 Nov 2010 17:17:11 -0800 (PST) Message-ID: <4CE1DB90.3000502@b1c1l1.com> Date: Mon, 15 Nov 2010 17:17:04 -0800 From: Benjamin Lee User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20101002 Lightning/1.0b3pre Thunderbird/3.1.4 MIME-Version: 1.0 To: Joerg Pulz References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigCAD3B4894700CB8002576647" Cc: freebsd-hackers@freebsd.org Subject: Re: [CFT+RFC] patch to buildworld with heimdal from ports X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2010 01:17:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCAD3B4894700CB8002576647 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/15/2010 02:08 PM, Joerg Pulz wrote: > Hi, >=20 > after the security/heimdal port was updated to the current heimdal > release and i added one missing function from base it is now possible t= o > completely buildworld src/ using the port for all Kerberos5/GSSAPI > enabled parts. Hi Joerg, I don't think that having the base system depend on a port is the right solution to resolving the libgssapi compatibility problems in base. Did you ever come across the old PR kern/147454 that I submitted in June? In it I included a src patch that replaced the base system's libgssapi with upstream Heimdal's, which resolved all libgssapi compatibility problems. That patch is now stale, but either way I haven't been able to draw enough attention to the issue to have it fixed.= --=20 Benjamin Lee http://www.b1c1l1.com/ --------------enigCAD3B4894700CB8002576647 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.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJM4duVAAoJEDQaOGXZe8jk4DEP/Rk1vwGgnyDSU7rQll116TQ6 NPcHh2+NnBfGpHDlglHXFmGNlgmPWTmvEvpOMjuxTjg5co9rHOHhe+3rZ2doXPWn P9/gK+iYgI06DhoBNwwG4DYocfihWte9+ymSIldoocOaIH/RztHXcrRNzzDw9GJJ wRAF6F3D1mLiv6uxYXKeCI971N6E7B3w3wPgz4UfqyYcwu7lAzcUNXXUuZ0nFdxl BEQ5su0XTvQamZT/IPxfDgGZ9GhsCUPakU1/ibIXLdsAkHVnl5iyWrD6gTpNH8N7 c4gz9VBaAfx1MUR9S8Ga1adQTp//JLz9K7JrObVtsjHbcyYVUfw4vTS5trNey234 1PUQXQC+N9ZTCuqdFjHrkUODtTYRq7d5BlyEtK+4jyTVJ3f/3Hx/3B8IDvtpdaev 4WOPqVzjsG/J96MJiFDgGhb5/quuYX75hovkLfGxYcUln+g0RUNgXvYpAnF8FzSi UwxoYkbokYMkQSd11VgfLxbaRhMbNbKaLrYXwO3L4SrqglwsHEgRa9wWqQCtTcHK 3dy105Ja7nUhALuaaKFqfdw/2HVTNYLfgnu6SoihKO2gB2aSfk1k2fDe67Rv5jmC WWk6UrG85qZOeTRIG4q62qhNMFmYPrDj5890ulOPJ3YsPjKSYl7OoiAQsWo6XwxV DOkdsK3PFnhed1SeVyUL =vsRE -----END PGP SIGNATURE----- --------------enigCAD3B4894700CB8002576647--