Date: Sat, 06 Oct 2001 14:41:01 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: Johann Visagie <wjv@FreeBSD.org> Cc: portmgr@FreeBSD.org, ports@FreeBSD.org Subject: Re: USE_LIBTOOL breakage in freebsd.port.mk Message-ID: <7m1ykhl40i.wl@waterblue.imgsrc.co.jp> In-Reply-To: <20011004152617.J21830@fling.sanbi.ac.za> References: <20011004152617.J21830@fling.sanbi.ac.za>
next in thread | previous in thread | raw e-mail | index | archive | help
At Thu, 4 Oct 2001 13:26:41 +0000 (UTC), Johann Visagie wrote: > I've now come across two packages - iODBC (http://www.iodbc.org/) and > ORBit-C++ (http://orbitcpp.sourceforge.net/) which ship with an autoconf > 2.13-generated configure script containing the following line: > > ltmain="$ac_aux_dir/ltmain.sh" > > The value of ${ltmain} is later tested for file existence in order to > determine whether to build the libtool script: > > if test -f "$ltmain"; then > <<create libtool>> > fi > > In updating/creating ports for these packages, I found that if USE_LIBTOOL is > defined, the patch-libtool target in bsd.port.mk munges the line where > ${ltmain} is defined to become: > > ltmain="--disable-ltlibs /usr/local/share/libtool/ltmain.sh" > > This of course fails the "test -f", with the result that libtool is never > created and the port build breaks. > > Attached is a patch for bsd.port.mk to work around the problem. Comments? It seems my problem on net-snmp (4.2.2-pre*) can be solved with this patch. Portmgr, is there a problem if I commit this patch? -- Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc. <kuriyama@FreeBSD.org> // FreeBSD Project 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?7m1ykhl40i.wl>