Re: mdate-sh vs. evil user/group names

2007-03-28 Thread Eric Blake
Ralf Wildenhues Ralf.Wildenhues at gmx.de writes: Hi Eric, Apologies for the delay. * Eric Blake wrote on Thu, Mar 01, 2007 at 11:24:14PM CET: mdate-sh fails miserably in the presence of user/group names that contain spaces (bad practice, but particularly common on cygwin). [...]

Re: automake/511: ./config.status in generated makefile conflicts with AM_MAKEFLAGS=-f alternativemakefilename

2007-03-28 Thread Ralf Wildenhues
[ http://lists.gnu.org/archive/html/automake-patches/2006-11/msg1.html ] * Ralf Wildenhues wrote on Sun, Nov 12, 2006 at 06:33:52PM CET: OK to apply? (make check is still running.) This passed back then (yes, I remember ;-) I applied the patch to HEAD and branch-1-10. The checkin

Re: fix coreutils' make distcheck: remove AC_CONFIG_LIBOBJ_DIR(lib)

2007-03-28 Thread Ralf Wildenhues
[ http://lists.gnu.org/archive/html/automake-patches/2006-10/msg00067.html ] * Ralf Wildenhues wrote on Tue, Oct 17, 2006 at 08:07:09PM CEST: * Stepan Kasal wrote on Tue, Oct 17, 2006 at 12:02:05PM CEST: I think that the patch has broken the error message in the procedure. Attached is a

mdate-sh borks on uid/gid containing a space

2007-03-28 Thread Dave Korn
Afternoon all, As the subject line says, mdate-sh can get badly confused if there are spaces in the textual version of the uid or gid. I don't know how often this happens on real unix systems, but it's a very common occurrence on Cygwin systems, causing this:

Lost in automatic dependencies

2007-03-28 Thread Stephane Bortzmeyer
It seems that my C program does not track dependencies. If I touch a .h, nothing is recompiled. I did *not* use no-dependencies. Reading the FM, it seems I should have automatic dependencies tracking but I do not have. automake (GNU automake) 1.9.6 gcc 4.1.2 or 3.3.3 GNU Make 3.81

Re: Lost in automatic dependencies

2007-03-28 Thread Ralf Wildenhues
Hi Stephane, * Stephane Bortzmeyer wrote on Wed, Mar 28, 2007 at 10:41:51PM CEST: It seems that my C program does not track dependencies. If I touch a .h, nothing is recompiled. I did *not* use no-dependencies. Hmm. Please show the configure output around checking dependency style. Please

Re: Lost in automatic dependencies

2007-03-28 Thread Ralf Wildenhues
* quoting myself: * Stephane Bortzmeyer wrote on Wed, Mar 28, 2007 at 10:41:51PM CEST: It seems that my C program does not track dependencies. If I touch a .h, nothing is recompiled. I did *not* use no-dependencies. More clues (sorry, hit the wrong key too early): does the Makefile in

Re: Lost in automatic dependencies

2007-03-28 Thread Stephane Bortzmeyer
On Wed, Mar 28, 2007 at 10:48:24PM +0200, Ralf Wildenhues [EMAIL PROTECTED] wrote a message of 16 lines which said: Please show the configure output around checking dependency style. gcc version 3.3.3 (NetBSD nb3 20040520) ... configure:19139: checking dependency style of cc configure:19229:

Re: Lost in automatic dependencies

2007-03-28 Thread Ralf Wildenhues
* Stephane Bortzmeyer wrote on Wed, Mar 28, 2007 at 11:06:31PM CEST: On Wed, Mar 28, 2007 at 10:48:24PM +0200, Ralf Wildenhues [EMAIL PROTECTED] wrote a message of 16 lines which said: Please show the configure output around checking dependency style. gcc version 3.3.3 (NetBSD nb3

Re: Lost in automatic dependencies

2007-03-28 Thread Stephane Bortzmeyer
On Wed, Mar 28, 2007 at 11:16:32PM +0200, Ralf Wildenhues [EMAIL PROTECTED] wrote a message of 27 lines which said: How exactly was configure invoked ./configure --config-cache and could you show the configure.ac up to AC_PROG_CXX? I did not invoke AC_PROG_CXX (there is no C++ in the

Re: Lost in automatic dependencies

2007-03-28 Thread Ralf Wildenhues
* Stephane Bortzmeyer wrote on Wed, Mar 28, 2007 at 11:33:16PM CEST: On Wed, Mar 28, 2007 at 11:16:32PM +0200, Ralf Wildenhues [EMAIL PROTECTED] wrote a message of 27 lines which said: and could you show the configure.ac up to AC_PROG_CXX? I did not invoke AC_PROG_CXX (there is no C++

Re: undefined macro

2007-03-28 Thread John Darrington
[ CCing to automake@gnu.org as this is an automake issue ] I had similar problems after upgrading to automake-1.10, which (because it wasn't available in Debian etch) I installed in /usr/local whereas all the m4 macros were in /usr. The solution I used was to create a file