From owner-freebsd-current@FreeBSD.ORG Tue Jul 6 12:06:32 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6D8F1065673 for ; Tue, 6 Jul 2010 12:06:32 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from unimail.uni-dortmund.de (mx1.HRZ.Uni-Dortmund.DE [129.217.128.51]) by mx1.freebsd.org (Postfix) with ESMTP id 7C4698FC1F for ; Tue, 6 Jul 2010 12:06:31 +0000 (UTC) Received: from [131.234.21.116] (baloo.cs.uni-paderborn.de [131.234.21.116]) (authenticated bits=0) by unimail.uni-dortmund.de (8.14.4/8.14.4) with ESMTP id o66BlIEm004661 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for ; Tue, 6 Jul 2010 13:47:19 +0200 (CEST) Message-ID: <4C3317C6.3020009@FreeBSD.org> Date: Tue, 06 Jul 2010 13:47:18 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.4) Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org References: <20100706085435.GC13238@deviant.kiev.zoral.com.ua> In-Reply-To: <20100706085435.GC13238@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Regression in GSSAPI/libxh509 linking? [PR bin/147175] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Jul 2010 12:06:33 -0000 Am 06.07.2010 10:54, schrieb Kostik Belousov: > On Tue, Jul 06, 2010 at 10:20:28AM +0200, Matthias Andree wrote: >> Please help: read PR bin/147175 and comment if you're knowledgeable about >> either run-time linking, KRB5/GSSAPI, or both :) > > You need to gather and show exact command that fails. Hi Kostik, thanks. I'd propose re-reading , particularly the "How to reproduce section", and ask specific questions that pop up afterwards. :-) > Shared object that references a symbol but does not record a dependency > on the object providing the symbol is the bug in the build of that object > (usually). In that case, Andrew's proposed patch (same URL as above, which see) would be the way to go, because it adds those dependencies to the Heimdal X.509 library build Makefile. However, I'm neither into -current nor into base system affairs. Any takers? Best regards -- Matthias Andree