On Sun, 2003-08-31 at 13:55, Atsuhito Kohda wrote: > From: Scott James Remnant <scott@netsplit.com> > Subject: Re: Bug#201935: Libtool script used in your package needs updating > Date: 20 Jul 2003 11:41:59 +0200 > > > > > $ libtoolize -cf > > This caused an error as; > > libtoolize -cf > libtoolize: unrecognized option `-cf' > Try `libtoolize --help' for more information. > > so I changed it as "libtoolize -c -f" then I got an error as; > > libtoolize -c -f > Yes, sorry about that... :o) > Remember to add `AC_PROG_LIBTOOL' to `configure.in'. > Using `AC_PROG_RANLIB' is rendered obsolete by `AC_PROG_LIBTOOL' > > so I replaced `AC_PROG_RANLIB' with `AC_PROG_LIBTOOL' > in top configure.in but still I got an error as; > You only need AC_PROG_LIBTOOL once, it just happens that the later version of libtool run AC_PROG_RANLIB for you so you don't need to do it yourself. > configure:18887: error: possibly undefined macro: AM_MAINTAINER_MODE > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > > What I should do in fact? > Looks like aclocal didn't find your automake m4 files ... if I were you I'd go back to your last-known-good TeX source and look *carefully* at the following files... configure.in /configure.ac Makefile.in aclocal.m4 ltmain.sh And find out which versions of Autoconf, Automake and libtool were used. Then make sure you use the same branch of each when updating. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
Attachment:
signature.asc
Description: This is a digitally signed message part