From owner-freebsd-ports@FreeBSD.ORG Sun Jul 6 10:48:51 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 91426399 for ; Sun, 6 Jul 2014 10:48:51 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49176265B for ; Sun, 6 Jul 2014 10:48:51 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1X3k02-0006Gl-5Y for freebsd-ports@freebsd.org; Sun, 06 Jul 2014 12:48:50 +0200 Date: Sun, 6 Jul 2014 12:48:50 +0200 From: Kurt Jaeger To: FreeBSD Ports Subject: Re: Bug 191256 - [PATCH] security/libgcrypt: update to 1.6.1 Message-ID: <20140706104850.GD2586@home.opsec.eu> References: <20140704132332.7a09caa5@scorpio> <20140705080355.GB2586@home.opsec.eu> <20140705225007.GD56726@home.opsec.eu> <20140706094658.GC2586@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140706094658.GC2586@home.opsec.eu> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2014 10:48:51 -0000 Hi! > > > > > Log see http://people.freebsd.org/~pi/misc/build-libgcrypt.txt > > > Hmm. I'm a bit confused now. I checked the newly linked libgcrypt.so.20 > > (located in src/.libs) and it seems to have all of the "missing" symbols in > > its symbol table, but all are undefined. I ran nm -D on the file and: > > The symbols are defined in cast5-amd64.S, but this file is not > added to libgcrypt.so. This needs to be fixed, then it probably works. Hm, it looks like most of the cipher/*-amd64.S files are not linked in. I prepared a bug report upstream: https://bugs.g10code.com/gnupg/issue1668 -- pi@opsec.eu +49 171 3101372 6 years to go !