Date: Fri, 27 May 2005 14:40:05 GMT From: Giorgos Keramidas <keramida@freebsd.org> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/81558: AC_PROG_LIBTOOL macro is not available to automake Message-ID: <200505271440.j4REe5VN030502@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/81558; it has been noted by GNATS. From: Giorgos Keramidas <keramida@freebsd.org> To: Markus Hoenicka <markus.hoenicka@mhoenicka.de> Cc: bug-followup@freebsd.org Subject: Re: misc/81558: AC_PROG_LIBTOOL macro is not available to automake Date: Fri, 27 May 2005 17:33:14 +0300 On 2005-05-27 14:16, Markus Hoenicka <markus.hoenicka@mhoenicka.de> wrote: > If configure.in calls the AC_PROG_LIBTOOL macro, the command sequence > > libtoolize15 --force --copy > aclocal19 --force > autoheader259 > automake19 --add-missing --force-missing > autoconf259 > > fails to build a usable configure script. The error message > indicates that the AC_PROG_LIBTOOL and AC_PROG_LD macros cannot be > expanded: > > configure.in:27: error: possibly undefined macro: AC_PROG_LD > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure.in:29: error: possibly undefined macro: AC_PROG_LIBTOOL I don't think using the autoconfXXX and automakeXXX ports for software that builds outside of the Ports is supported. Please use the devel/gnu-autoconf, devel/gnu-automake and devel/gnu-libtool ports for this sort of thing. These will install full versions of the autotools in /usr/local/gnu-autotools and can be used by setting the PATH to point first to /usr/local/gnu-autotools/bin and then to /usr/local/bin. - Giorgos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200505271440.j4REe5VN030502>