Jason L Tibbitts III [EMAIL PROTECTED] writes:
MG == Mikhael Goikhman [EMAIL PROTECTED] writes:
MG It should be autoreconf; automake, so the first automake may not
MG help. Or maybe aclocal; automake; autoconf; autoheader.
Do I need to change how snapshots are built? This looks like what
DE == Dan Espen [EMAIL PROTECTED] writes:
DE Jason, I think you might have missed Mikhael's answer.
Ah, there was an answer in there. I've added the call to aclocal;
let's see how another snapshot builds. (Sorry about the two false
starts, BTW.)
- J
--
Visit the official FVWM web page at
On Thu, Feb 28, 2002 at 09:04:05AM -0500, Dan Espen wrote:
Jason L Tibbitts III [EMAIL PROTECTED] writes:
MG == Mikhael Goikhman [EMAIL PROTECTED] writes:
MG It should be autoreconf; automake, so the first automake may not
MG help. Or maybe aclocal; automake; autoconf; autoheader.
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
MG == Mikhael Goikhman [EMAIL PROTECTED] writes:
MG It should be autoreconf; automake, so the first automake may not
MG help. Or maybe aclocal; automake; autoconf; autoheader.
Do I need to change how snapshots are built? This looks like what
caused this morning's failure. The current script
binBnQjdb5EB5.bin
Description: application/fw
Mikhael, with your latest commit I get a message from automake:
fvwm/Makefile.am:30: variable `FT2_LIBS' not defined
(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
