Re: aclocal-1.8/m4_include behaving oddly

2003-12-23 Thread Phil Edwards
On Mon, Dec 22, 2003 at 03:17:54PM +0100, Andreas Schwab wrote: > Phil Edwards <[EMAIL PROTECTED]> writes: > > > But now we're trying to move to the latest released tools, and aclocal > > 1.8 flags errors dealing with that block: > > > > aclocal:

aclocal-1.8/m4_include behaving oddly

2003-12-20 Thread Phil Edwards
One of the GCC runtime libraries (libstdc++-v3) has for years contained the following lines in acinclude.m4: m4_include([../libtool.m4]) dnl The lines below arrange for aclocal not to bring an installed dnl libtool.m4 into aclocal.m4, while still arranging for automake to dnl add a

Change in dejagnu generated rules?

2002-12-19 Thread Phil Edwards
When AUTOMAKE_OPTIONS contains dejagnu, one of the generated rules is check-am: $(MAKE) $(AM_MAKEFLAGS) check-DEJAGNU I could have sworn that at some time in the not-too-distant past, the -k flag would also be automatically passed to the sub-make, $(MAKE) -k $(AM_MAKEFLAGS)

Re: what is this shell call trying to solve?

2002-01-22 Thread Phil Edwards
> That code is there support non-srcdir builds in the face of 'make's > with broken VPATH implementations. Ah, okay. Having never worked with such a 'make' this caught me off guard. Thanks! Phil

what is this shell call trying to solve?

2002-01-22 Thread Phil Edwards
Been playing with 1.5 and have been pretty pleased with the support for source files in subdirectories. I have noticed however something which strikes me as odd: % make make all-am make[1]: Entering directory `/tmp/pme/foo' source='/home/pme/easysems/main.cc' object='main.o' libtoo