Hello Martin, * Martin Koeppe wrote on Tue, Apr 03, 2007 at 09:10:48PM CEST: > > However, I now found out why 'make' is called. Interix make has some > standard build rules in /usr/share/mk/sys.mk, which also define > MAKE=make. When calling "make.itx -r", then MAKE and also MAKEFLAGS > are set correctly and sys.mk isn't read. > > When using Interix make without -r, AC_PROC_MAKE_SET isn't smart > enough to check if MAKE is not just set, but also set correctly.
Yeah, I guess Autoconf needs a patch there. Could you try configuring with ./configure MAKE=make.itx ac_cv_prog_make_make_itx_set=no please? If an autoconf rerun is triggered, you _need_ 2.61 to avoid a related bug. > When OTOH one calls > $ ./configure MAKE=make.itx MAKEFLAGS=-r > and later > $ make.itx -r > then libtool and/or automake apparently isn't smart enough to call > recursive makes as "$(MAKE) $(MAKEFLAGS)" instead of just "$(MAKE)", > so the second recursion fails again. Oh, for that you can try to use AM_MAKEFLAGS. > Why, however, ./configure is called a second time with make.itx and > not with make.gnu, I couldn't yet figure out. Maybe someone has some > hints? Not yet. Maybe we still have some nonportable construct in there; or Interix make figures something out wrongly. Dunno. Cheers, and thanks, Ralf
