On Tue, 2008-03-04 at 10:44 +0100, Hans Aberg wrote: > On 4 Mar 2008, at 10:24, Axel Simon wrote: > > >>> You need to run aclocal before running autoconf. > >> > >> It id not work for me. > >> > >>> If you don't do that, autoconf will not see the macro definitions > >> for > >>> AM_INIT_AUTOMAKE, AM_CONDITIONAL, GTKHS_PROG_CHECK_VERSION, ... > >> > >> I think autoconf runs aclocal, but running aclocal first did not > >> work > >> for me. > > > > I agree with Ralf: autoconf alone will not work. > > Running autoconf once does not work, but running it twice do. It runs > aclocal, butt running aclocal separately first does not work - it has > to be within the program autoconf.
Nothing in the documentation says that autoconf runs aclocal. On a clean tree, I can run autoconf twice, the first time getting messages about missing macros, the second time it's quiet since it keeps some information in autom4ate.cache/. This still leads to a broken 'configure' that complains that the AM_INIT_AUTOMAKE command was not found. This is because aclocal needs to be run first. I need to understand why rm -rf autom4te.cache/ aclocal.m4 configure aclocal autoheader automake autoconf or simply rm -rf autom4te.cache/ aclocal.m4 configure autoreconf doesn't work. > You may disagree with my computer, but I doubt it will change its > mind by that. :-) There is no point in exchanging 50+ emails about what happens on your computer or not if it doesn't help to resolve the issue. The problem is that I cannot reproduce your problem, not get any information that helps me understand why it doesn't work on your computer. I would help if you ran the above programs with some tracing and debugging options in order to understand where it goes wrong. I've just looked at the very first email in the gtk2hs-users archives. You state that you have automake 1.9.6. Our web-site says that 1.9 gives errors on Debian systems and that you need automake 1.10. Do you now have automake 1.10 on your system? Axel.
