[PATCH] bootstrap: check for AC_PROG_LIBTOOL as well as AM_PROG_LIBTOOL

2008-10-04 Thread Jim Meyering
>From 1ff16a1235ed546f04b219966a9142a2334a7b4b Mon Sep 17 00:00:00 2001 From: Jim Meyering <[EMAIL PROTECTED]> Date: Sun, 5 Oct 2008 08:24:04 +0200 Subject: [PATCH] bootstrap: check for AC_PROG_LIBTOOL as well as AM_PROG_LIBTOOL * build-aux/bootstrap: Check for AC_PROG_LIBTOOL, as well as the obs

Patch to check for required programs when building from source checkout

2008-10-04 Thread Ed Avis
A few tools are required to build coreutils from a git checkout, but not checked in a friendly way. This patch adds checks to bootstrap and configure. Oh, and updates automake to 1.10.1, which appears to work. diff --git a/bootstrap b/bootstrap index 438a145..0232ae9 100755 --- a/bootstrap ++

cp -u should skip copying a file to itself

2008-10-04 Thread Ed Avis
% touch foo foo % cp -u foo foo && echo yes cp: `foo' and `foo' are the same file I expected that since -u says -u, --update copy only when the SOURCE file is newer than the destination file or when the destination file is missing it would not attempt to copy

Re: tee logs no output if stdout is closed

2008-10-04 Thread Bruno Haible
Jim Meyering wrote: > > You can distinguish close_stream and close_stdout. close_stream is library > > code, > > close_stdout is not. What about a 'bool ignore_epipe' that influences the > > behaviour of close_stdout? Whereas the library code that called close_stream > > has to check against EOF/E

Re: tee logs no output if stdout is closed

2008-10-04 Thread Jim Meyering
Bruno Haible <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> > ... if SIGPIPE is blocked or ignored. >> > >> >> which is not generally recommended. >> >> In some contexts. Some environments (mis-configured login/csh) have >> resulted in the default SIGPIPE handler being SIG_IGN. > > I agree t

Re: cp --preserve=mode not right on rh4 and nfs

2008-10-04 Thread Jim Meyering
Jim Meyering <[EMAIL PROTECTED]> wrote: > Warren L Dodge <[EMAIL PROTECTED]> wrote: >> I have built coreutils-6.12 on a GNU/Linux RedHat3 system. When I use >> the "cp" command with the --preserve=mode,timestamps switch there is a >> problem where a copy to a nfs mounted file system does not set th

Re: cp --preserve=mode not right on rh4 and nfs

2008-10-04 Thread Andreas Schwab
Warren L Dodge <[EMAIL PROTECTED]> writes: > I have built coreutils-6.12 on a GNU/Linux RedHat3 system. When I use > the "cp" command with the --preserve=mode,timestamps switch there is a > problem where a copy to a nfs mounted file system does not set the > timesamp properly. That looks like tha

Re: cp --preserve=mode not right on rh4 and nfs

2008-10-04 Thread Jim Meyering
Warren L Dodge <[EMAIL PROTECTED]> wrote: > I have built coreutils-6.12 on a GNU/Linux RedHat3 system. When I use > the "cp" command with the --preserve=mode,timestamps switch there is a > problem where a copy to a nfs mounted file system does not set the > timesamp properly. > > I show examples be