Date: Tue, 5 Jul 2005 17:38:53 +0300 From: Giorgos Keramidas <keramida@freebsd.org> To: Marco Molteni <molter@tin.it> Cc: freebsd-hackers@freebsd.org Subject: Re: building something from CVS with GNU autotools Message-ID: <20050705143853.GB2522@beatrix.daedalusnetworks.priv> In-Reply-To: <20050705161445.1d47440c.molter@tin.it> References: <20050705161445.1d47440c.molter@tin.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-07-05 16:14, Marco Molteni <molter@tin.it> wrote: > I pulled all my hair and lost my sanity. I searched mailing lists ang > google, found a lot of people with my same problem but never a > definitive solution. > > Problem is when trying to build on fbsd no matter which program out of > CVS (ie: not a release) which uses GNU autotools. > > After patching ./autogen.sh to use the versioned autotools, I get the > standard error (standard because google is full of it): > > ./ltconfig: ./ltconfig: No such file or directory > configure: error: libtool configure failed > > I tried also building a directory full of symlinks and putting it at > the beginning of my PATH, to be sure to catch any invocation of the > autotools stuff: > > molter@gattaccio[~]$ ls autodamage > aclocal@ -> /usr/local/bin/aclocal15 > autoconf@ -> /usr/local/bin/autoconf259 > autoheader@ -> /usr/local/bin/autoheader259 > > and so on, but I still hit the wall. > > In my case I am trying to compile the CVS version of silky > (http://silky.sourceforge.net/), but as I said silky is a program like > another. > > I also saw there is a /usr/ports/Mk/bsd.autotools.mk makefile with > some comments in it, but it is not clear to me how to reuse that stuff > outside of a port. > > Is there a way to solve my problems, without requiring any fbsd user > to become a master of the weird and (censured comments) autotools ? Yes. This question comes up very frequently and has been answered several times. My preferred solution to the autotools "problem", which works admirably well on all systems I've tried it so far (FreeBSD, Solaris and Linux) is to install a local version of the latest autotools in /opt/autotools and prepend /opt/autotools/bin to my PATH. A simpler solution, if you don't really want to go into the trouble of downloading the source tarballs for autoconf, automake and libtool, compiling everything yourself and installing in /opt/autotools, is to use the devel/gnu-* ports that install autoconf, automake and libtool in /usr/local/gnu-autotools and prepend that to your PATH. - Giorgos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050705143853.GB2522>