Date: Thu, 9 Oct 2014 18:53:21 +0200 From: Tijl Coosemans <tijl@FreeBSD.org> To: Hajimu UMEMOTO <ume@FreeBSD.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r370526 - head/security/cyrus-sasl2-gssapi Message-ID: <20141009185321.5db18929@kalimero.tijl.coosemans.org> In-Reply-To: <201410091318.s99DISxR078486@svn.freebsd.org> References: <201410091318.s99DISxR078486@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 9 Oct 2014 13:18:28 +0000 (UTC) Hajimu UMEMOTO <ume@FreeBSD.org> wrote: > Author: ume > Date: Thu Oct 9 13:18:28 2014 > New Revision: 370526 > URL: https://svnweb.freebsd.org/changeset/ports/370526 > QAT: https://qat.redports.org/buildarchive/r370526/ > > Log: > Include RPATH in the libs, again. > It seems that USES=libtool doesn't rewrite ${LIBTOOL} in > a configure script to use ${LOCALBASE}/bin/libtool like > bsd.autotools.mk did. > So, rewrite it explicitly for workaround. > > PR: 194176 > Submitted by: jhujhiti__at__adjectivism.org Can you ask upstream to run 'autoreconf -f -i'? It will update all the build scripts. For instance, the version of libtool that is currently included in the distfile is almost 15 years old. Ideally the cyrus-sals2 ports should also do that (by adding USES=autoreconf) instead of this hack. The problem with this hack, and the reason why USES=libtool does not use it, is that libtool is a generated script with hardcoded values for CC, LD, and a number of other tools and flags. And the tools used to build security/cyrus-sasl2-gssapi are not necessarily the same as the ones used to build devel/libtool.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141009185321.5db18929>