Ade Lovett <[EMAIL PROTECTED]> writes:
> On Mar 14, 2006, at 05:10 , Dag-Erling Smørgrav wrote:
> > It used to be a breeze. It is now considerably harder, because
> > gnu-autoconf's aclocal can't find libtool.ac, so you can't build
> > anything that uses libtool.
> I don't see a libtool.ac anywhere within devel/{,gnu}auto{conf,make}*
libtool.m4, actually. devel/gnu-libtool installs it:
[EMAIL PROTECTED] ~% pkg_info -L gnu-libtool-1.5.20 | grep aclocal
/usr/local/gnu-autotools/share/aclocal/libtool.m4
/usr/local/gnu-autotools/share/aclocal/ltdl.m4
/usr/local/gnu-autotools/share/libtool/libltdl/aclocal.m4
devel/libtool15 also installs it, but aclocal can't find it:
[EMAIL PROTECTED] ~% pkg_info -L libtool-1.5.22_2| grep aclocal
/usr/local/share/aclocal/libtool.m4
/usr/local/share/aclocal/ltdl.m4
/usr/local/share/libtool/libltdl/aclocal.m4
[EMAIL PROTECTED] ~/projects/openpam% sh -x autogen.sh
+ aclocal
+ libtoolize --copy --force
You should update your `aclocal.m4' by running aclocal.
+ autoheader
+ automake -a -c --foreign
configure.ac: installing `./install-sh'
configure.ac: installing `./missing'
bin/su/Makefile.am: installing `./depcomp'
lib/Makefile.am:7: Libtool library used but `LIBTOOL' is undefined
lib/Makefile.am:7:
lib/Makefile.am:7: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
lib/Makefile.am:7: to `configure.ac' and run `aclocal' and `autoconf' again.
lib/Makefile.am: installing `./compile'
modules/pam_deny/Makefile.am:6: Libtool library used but `LIBTOOL' is undefined
modules/pam_deny/Makefile.am:6:
modules/pam_deny/Makefile.am:6: The usual way to define `LIBTOOL' is to add
`AC_PROG_LIBTOOL'
modules/pam_deny/Makefile.am:6: to `configure.ac' and run `aclocal' and
`autoconf' again.
modules/pam_permit/Makefile.am:6: Libtool library used but `LIBTOOL' is
undefined
modules/pam_permit/Makefile.am:6:
modules/pam_permit/Makefile.am:6: The usual way to define `LIBTOOL' is to add
`AC_PROG_LIBTOOL'
modules/pam_permit/Makefile.am:6: to `configure.ac' and run `aclocal' and
`autoconf' again.
modules/pam_unix/Makefile.am:7: Libtool library used but `LIBTOOL' is undefined
modules/pam_unix/Makefile.am:7:
modules/pam_unix/Makefile.am:7: The usual way to define `LIBTOOL' is to add
`AC_PROG_LIBTOOL'
modules/pam_unix/Makefile.am:7: to `configure.ac' and run `aclocal' and
`autoconf' again.
+ autoconf
configure.ac:10: error: possibly undefined macro: AC_DISABLE_STATIC
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:11: error: possibly undefined macro: AC_PROG_LIBTOOL
Compare and contrast what happens with the old gnu-libtool installed:
[EMAIL PROTECTED] ~/projects/openpam% sh -x autogen.sh
+ aclocal
+ libtoolize --copy --force
You should update your `aclocal.m4' by running aclocal.
+ autoheader
+ automake -a -c --foreign
+ autoconf
> The goal here is to provide the exact same autotools functionality
> (libtool, autoconf, automake) as is present on other systems,
> notably Linux and NetBSD pkgsrc. The recent libtool conversion has
> proven itself to work (otherwise there wouldn't be very many
> packages for the upcoming 5.5/6.1 releases).
The great majority of ports don't use aclocal, because the tarballs
ship with pre-generated aclocal and configure scripts. If you didn't
already know and understand that, you have no business messing with
the autotool ports.
> I'm really not interested in, nor do I have the time for, religious
> arguments.
This is not a religious argument. It's a very simple technical
argument: the GNU autotools used to work, now they don't.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
