Re: $(EXEEXT) in TESTS required?

2006-01-24 Thread Bruno Haible
Ralf Corsepius wrote: > Due to lack of a mingw toolchain, I can't tell you exactly what goes > wrong for you. > > 3 likely candidates: > * The cross gcc doesn't produce *.exe's (This would be a gcc bug). > * You are not correctly invoking configure. > * Makefile bug somewhere. Is there need to hyp

Re: $(EXEEXT) in TESTS required?

2006-01-24 Thread Bruno Haible
Ralf Wildenhues wrote: > > check_PROGRAMS = test-lock$(EXEEXT) > > > > TESTS = test-lock > ... > What about @substituted@ values? TESTS = @substituted@ You could treat it like @substituted@ in check_PROGRAMS, namely - assume that $(EXEEXT) is contained in the substituted value, - warn if EXTR

Re: $(EXEEXT) in TESTS required?

2006-01-24 Thread Ralf Corsepius
On Tue, 2006-01-24 at 13:15 +0100, Simon Josefsson wrote: > Ralf Corsepius <[EMAIL PROTECTED]> writes: > > > On Mon, 2006-01-23 at 21:51 +0100, Bruno Haible wrote: > >> [For the automake people: The problem is that a Makefile.am snippet like > >> > >> TESTS = test-lock > >> check_PROGRA

Re: $(EXEEXT) in TESTS required?

2006-01-24 Thread Simon Josefsson
Ralf Corsepius <[EMAIL PROTECTED]> writes: > On Mon, 2006-01-23 at 21:51 +0100, Bruno Haible wrote: >> [For the automake people: The problem is that a Makefile.am snippet like >> >> TESTS = test-lock >> check_PROGRAMS = test-lock >> test_LOCK_LDFLAGS = -lmyspeciallib >> >> when cr

Re: $(EXEEXT) in TESTS required?

2006-01-24 Thread Ralf Wildenhues
Hi Bruno, * Bruno Haible wrote on Mon, Jan 23, 2006 at 09:51:57PM CET: > > ... > noinst_PROGRAMS = > check_PROGRAMS = test-lock$(EXEEXT) > > TESTS = test-lock > > check-am: all-am > $(MAKE) $(AM_MAKEFLAGS) $(check_PROGRAMS) > $(MAKE) $(AM_MAKEFLAGS) check-TESTS > > check-TESTS: $(T