Re: 1.10a instspc.test failure

Ralf Wildenhues [EMAIL PROTECTED] writes: -is called. The value can contain newlines. +is called. The value can contain all ASCII characters except for +the @code{NUL} character and carriage return; newline is ok to use. If we can assume POSIX conformance with a reasonable C locale, the

Re: problem with a test that is expected to fail, on cygwin only...

* Brian Dessent wrote on Tue, Jan 16, 2007 at 03:33:27AM CET: Ed Hartnett wrote: TESTFILES = nctst tst_failure [...] TESTS = $(TESTFILES) run_nc_tests.sh XFAIL_TESTS = tst_failure [...] XFAIL: tst_failure [...] FAIL: tst_failure.exe Notice the difference? You probably should

Re: problem with a test that is expected to fail, on cygwin only...

Quoting Ralf Wildenhues [EMAIL PROTECTED]: * Brian Dessent wrote on Tue, Jan 16, 2007 at 03:33:27AM CET: Ed Hartnett wrote: TESTFILES = nctst tst_failure [...] TESTS = $(TESTFILES) run_nc_tests.sh XFAIL_TESTS = tst_failure [...] XFAIL: tst_failure [...] FAIL: tst_failure.exe Notice

Re: automake/514: check_JAVA files are always compiled

Thomas Schwinge wrote: Hello! On Wed, Jan 10, 2007 at 07:35:35PM +0100, Ralf Wildenhues wrote: * Roberto Bagnara wrote on Fri, Dec 22, 2006 at 03:17:21PM CET: The subject says all. Is there any workaround? check_JAVA files are always compiled, not only in case of `make

Re: automake/514: check_JAVA files are always compiled

Thomas Schwinge wrote: Hello! On Wed, Jan 10, 2007 at 07:35:35PM +0100, Ralf Wildenhues wrote: * Roberto Bagnara wrote on Fri, Dec 22, 2006 at 03:17:21PM CET: The subject says all. Is there any workaround? check_JAVA files are always compiled, not only in case of `make check'. Quoting 'info

Re: Multiple lex scanners? How?

On Mon, Jan 15, 2007 at 04:52:37PM -0700, Bob Proulx wrote: Multiple flex generated scanners are giving me trouble with duplicate symbols. I am using automake-1.10. What is the best practice for organizing a program that includes multiple lex generated scanners? I am using the