On 27 Feb 2002 06:26:48 +0100, Dominik Vogt wrote: > > Mikhael, with your latest commit I get a message from automake: > > fvwm/Makefile.am:30: variable `FT2_LIBS' not defined
I did not add FT2 code, but it seems ok at a glance. > (one for each Makefile). This only goes away after I run > autoreconf and then automake again. I assume this is a bug in the > Makefile setup. To get a proper build I now have to call > > $ automake; autoreconf; automake; autoreconf It should be "autoreconf; automake", so the first automake may not help. Or maybe "aclocal; automake; autoconf; autoheader". I didn't need to run "autoreconf; automake; ./configure; make" twice. Anyway, I don't think we may fix this Makefile circular dependancies hell. * autoreconf is a script manipulating aclocal + autoconf + autoheader * aclocal produces aclocal.m4 from acinclude.m4 * automake produces Makefile.in files from Makefile.am files * autoconf produces configure from configure.in and aclocal.m4 * autoheader produces config.h.in from configure.in * configure produces Makefile files from Makefile.in files * configure produces config.h from config.h.in * configure produces executable config.status to rebuild files from *.in * config.status --recheck regenerates itself from configure * make _should_ run everything above automatically using Makefile Now you may guess what happens when Makefile itself should be regenerated when you issue "make foobar". I.e. it should first produce a new Makefile instead of the currently run one, and then rerun "make foobar" on it. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
