Date: Thu, 27 Dec 2001 12:42:37 -0500 (EST) From: Joe Clarke <marcus@marcuscom.com> To: freebsd-ports@FreeBSD.ORG Subject: Re: Problems with porting and libtool Message-ID: <20011227124227.V11529-100000@shumai.marcuscom.com> In-Reply-To: <20011227123123.R11529-100000@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Nevermind, I found my answer in the archives. Thanks.
Joe
On Thu, 27 Dec 2001, Joe Clarke wrote:
> I'm having a problem creating a port that uses libtool. The problem
> revolves around bsd.port.mk. I'm hoping someone has run into this before.
> bsd.port.mk, if USE_LIBTOOL = yes says to substitute the following for
> ltmain:
>
> ${LIBTOOLFLAGS} $${LIBTOOLDIR}/ltmain.sh
>
> This effectively sets ltmain to
>
> <my libtool flags> /usr/local/share/libtool/ltmain.sh
>
> Unfortunately, <my libtool flags> is not empty. This changes ltmain from
> a file specification to a CLI command. This breaks a test -f in
> configure, and libtool is never generated.
>
> My workaround is to hardcode a new variable in configure, ltmain_file that
> points to /usr/local/share/libtool/ltmain.sh without any CLI arguments.
> This will allow the tests to succeed. Has anyone else seen this before?
> Could this be a bug in bsd.port.mk? Thanks.
>
> Joe
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-ports" in the body of the message
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011227124227.V11529-100000>