Re: [Zapping-misc] Re: Bugs and thanks!
Status: Alpha
Brought to you by:
mschimek
|
From: Michael H. S. <msc...@us...> - 2001-10-29 21:32:32
|
Nate Dannenberg wrote: > > Please add the files > codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 > progtest.m4 > from the /usr/share/aclocal directory to your autoconf macro directory > or directly to your aclocal.m4 file. > You will also need config.guess and config.sub, which you can get from > ftp://ftp.gnu.org/pub/gnu/config/. > > Making ./aclocal.m4 writable ... > Running libtoolize... > You should add the contents of `/usr/share/aclocal/libtool.m4' to > `aclocal.m4'. I think these warnings are bogus. > Running aclocal -I macros ... > aclocal: configure.in: 302: macro `AM_PATH_LIBGLADE' not found in library > aclocal: configure.in: 308: macro `AM_GNU_GETTEXT' not found in library Humble observation: The errors reported by Dirk Vornheder in thread "[Zapping-misc] autogen.sh doesn't work", Oct 15, show a similar pattern but I don't agree the autoconf suggestion, aclocal is part of the automake package. The aclocal I use, from automake 1.4, on a heavily patched SuSE 6.2, is configured w/prefix /usr. aclocal --verbose lists: Found macro AM_GNU_GETTEXT in /usr/share/aclocal/gettext.m4: 295 Found macro AM_PROG_LIBTOOL in /usr/share/aclocal/libtool.m4: 421 Found macro AM_PATH_LIBGLADE in /usr/share/aclocal/libglade.m4: 7 Found macro AM_INIT_AUTOMAKE in /usr/share/aclocal/init.m4: 10 I compared the aclocal script from automake 1.5, GNU .tgz, which seems to differ mainly in scanning -I macros first. The prefix defaults to /usr/local, so it scans /usr/share/aclocal for the files above, to no avail on my system. Except for > automake: src/Makefile.am: Assembler source seen but `AS' not defined > in `configure.in' > automake: src/Makefile.am: Assembler source seen but `ASFLAGS' not > defined in `configure.in' which are probably checks introduced in automake 1.5 and can be ignored, no more errors were reported after creating symlinks as a temporary fix. I have no explanation how autogen.sh should work for 0.6.1 in the same environment, but it's possible the Zapping packages being are already automake/conf'ed compile just fine despite disagreement over the correct aclocal path. Michael |