Date: Tue, 20 Jun 2006 18:37:33 +0200 From: Csaba Henk <csaba-ml@creo.hu> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: freebsd-ports@freebsd.org Subject: Re: keeping up with "gnu-libtool -> libtool15" Message-ID: <20060620163733.GU49983@beastie.creo.hu> In-Reply-To: <20060620140808.t9ta79szk0gwokws@netchild.homeip.net> References: <slrne9f52r.esg.csaba@beastie.creo.hu> <20060620091630.4uid5rgn4000cccg@netchild.homeip.net> <20060620080815.GS49983@beastie.creo.hu> <20060620103357.fg7pmhilckc0wgc0@netchild.homeip.net> <20060620100301.GT49983@beastie.creo.hu> <20060620140808.t9ta79szk0gwokws@netchild.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 20, 2006 at 02:08:08PM +0200, Alexander Leidinger wrote:
> I had to jump around a lot. I even forced the autotools and libtool to
> copy/link the missing stuff. I called the usage for each program
> (aclocal, autoheader, autoconf, automake, libtool) and looked for
> "force" and "copy missing bits" switches.
> [...]
> Ah... yes... I created a directory with symlinks and added it to the path.
OK, so for the example in question (FUSE) the following did the job:
ln -s /usr/local/share/aclocal/libtool.m4 .
(export PATH=/usr/local/gnu-autotools/bin:$PATH && libtoolize &&
aclocal -I . && autoheader && autoconf && automake -a)
It works without/regardless of the dirlist hack.
Thanks for your tips.
Anyway, I still maintain that it is a fine idea that you can get at a
Linux/Rest Of The World compatilbe autotools environment simply by
adjusting $PATH, and that breaking this scheme so that we end up
srtuggling in a swamp of witty hacks is a Bad Idea.
Hmm, would it make sense to file a PR for resurrecting gnu-libtool?
Regards,
Csaba
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060620163733.GU49983>