From owner-freebsd-ports@FreeBSD.ORG Sun Jan 4 16:36:45 2015 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 895F7FCF for ; Sun, 4 Jan 2015 16:36:45 +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 4660112BA for ; Sun, 4 Jan 2015 16:36:45 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1Y7oAV-00072t-QX for ports@freebsd.org; Sun, 04 Jan 2015 17:36:43 +0100 Date: Sun, 4 Jan 2015 17:36:43 +0100 From: Kurt Jaeger To: ports@freebsd.org Subject: Re: libmcrypt: configure fails for shared lib on freebsd 10.x [patch] Message-ID: <20150104163643.GR44537@home.opsec.eu> References: <000001d02836$d4b45f00$7e1d1d00$@mgedv.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001d02836$d4b45f00$7e1d1d00$@mgedv.net> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2015 16:36:45 -0000 Hi! > i'm kinda rookie, but there's a bug in the libmcrypt configure script, that > causes the libmcrypt shared library to never get built on freebsd 10.x. If you build the port security/libmcrypt, I see a shared lib being built: ./work/stage/usr/local/lib/libmcrypt.so.4.4.8 So what exactly do you mean with 'it does not get build' ? -- pi@opsec.eu +49 171 3101372 5 years to go !