new snapshot (rm fixes and new program: mktemp)

2007-10-08 Thread Jim Meyering
In addition to adding mktemp, I've fixed a few low-probability bugs in rm. This also includes a lot of new code from gnulib, by virtue of coreutils now requiring the vasprintf-posix module (mostly for non-POSIX systems), so please give this a work-out if you haven't built a snapshot recently:

Re: new snapshot (rm fixes and new program: mktemp)

2007-10-08 Thread Mike Frysinger
On Monday 08 October 2007, Jim Meyering wrote: In addition to adding mktemp thanks for this so please give this a work-out if you haven't built a snapshot recently: chcon fails on my non-selinux system during `make check` ... looks like it should be an XFAIL when selinux support is disabled

Re: new snapshot (rm fixes and new program: mktemp)

2007-10-08 Thread Jim Meyering
Mike Frysinger [EMAIL PROTECTED] wrote: ... chcon fails on my non-selinux system during `make check` ... looks like it should be an XFAIL when selinux support is disabled Thanks for the quick feedback. I presume you mean the root-only tests/misc/chcon test (btw, it works for me) If so, please

Re: new snapshot (rm fixes and new program: mktemp)

2007-10-08 Thread Mike Frysinger
On Monday 08 October 2007, Jim Meyering wrote: Mike Frysinger [EMAIL PROTECTED] wrote: chcon fails on my non-selinux system during `make check` ... looks like it should be an XFAIL when selinux support is disabled Thanks for the quick feedback. I presume you mean the root-only

Re: new snapshot (rm fixes and new program: mktemp)

2007-10-08 Thread Jim Meyering
Mike Frysinger [EMAIL PROTECTED] wrote: On Monday 08 October 2007, Jim Meyering wrote: Mike Frysinger [EMAIL PROTECTED] wrote: chcon fails on my non-selinux system during `make check` ... looks like it should be an XFAIL when selinux support is disabled Thanks for the quick feedback. I

Re: new snapshot (rm fixes and new program: mktemp)

2007-10-08 Thread Mike Frysinger
On Monday 08 October 2007, Jim Meyering wrote: This ought to make it skip: --- a/tests/misc/chcon +++ b/tests/misc/chcon +. $srcdir/../selinux this fixed it for me -mike signature.asc Description: This is a digitally signed message part. ___

Re: [PATCH] Command line parsing of ls, tail and wc with genparse

2007-10-08 Thread Jim Meyering
[EMAIL PROTECTED] (Michael Geng) wrote: On Sun, Oct 07, 2007 at 09:47:31AM +0200, Jim Meyering wrote: [EMAIL PROTECTED] (Michael Geng) wrote: ... The text is partitioned exactly as it is in the existing code of tail.c (I'm looking at a cvs archive copy from sept 9). This is from tail.c:

Re: new snapshot (rm fixes and new program: mktemp)

2007-10-08 Thread Bauke Jan Douma
Jim Meyering wrote on 08-10-07 11:05: In addition to adding mktemp, I've fixed a few low-probability bugs in rm. This also includes a lot of new code from gnulib, by virtue of coreutils now requiring the vasprintf-posix module (mostly for non-POSIX systems), so please give this a work-out if you

Re: new snapshot (rm fixes and new program: mktemp)

2007-10-08 Thread Bauke Jan Douma
Jim Meyering wrote on 08-10-07 11:05: In addition to adding mktemp, I've fixed a few low-probability bugs in rm. This also includes a lot of new code from gnulib, by virtue of coreutils now requiring the vasprintf-posix module (mostly for non-POSIX systems), so please give this a work-out if you

Re: new snapshot (rm fixes and new program: mktemp)

2007-10-08 Thread Jim Meyering
Bauke Jan Douma [EMAIL PROTECTED] wrote: Jim Meyering wrote on 08-10-07 11:05: In addition to adding mktemp, I've fixed a few low-probability bugs in rm. This also includes a lot of new code from gnulib, by virtue of coreutils now requiring the vasprintf-posix module (mostly for non-POSIX

Re: new snapshot (rm fixes and new program: mktemp)

2007-10-08 Thread Jim Meyering
Bauke Jan Douma [EMAIL PROTECTED] wrote: Jim Meyering wrote on 08-10-07 11:05: In addition to adding mktemp, I've fixed a few low-probability bugs in rm. This also includes a lot of new code from gnulib, by virtue of coreutils now requiring the vasprintf-posix module (mostly for non-POSIX

Re: Fwd: Re: error.c: Unknown system error should report errno value

2007-10-08 Thread Martin Koeppe
Hi Jim, hi Bruno, On Sat, 6 Oct 2007, Jim Meyering wrote: Bruno Haible [EMAIL PROTECTED] wrote: Martin Koeppe wrote: The Interix libc is built with MSVC. MSVC has no long double data type. Ok, it understands long double, but always maps that to 64-bit double. So libc's printf(), when it

Re: [RFC] linecut addition

2007-10-08 Thread Jim Meyering
Steven Schubiger [EMAIL PROTECTED] wrote: Jim Meyering [EMAIL PROTECTED] wrote: Before coding further, I strongly urge you to nail down the specification -- publicly. Put it this way: write enough details that someone reading your description in a man page would not be disappointed.

Re: Fwd: Re: error.c: Unknown system error should report errno value

2007-10-08 Thread Bruno Haible
Martin Koeppe wrote: Is seq segfaulting on mingw and BeOS, too? I just tested snapshot 316 and it unfortunately doesn't work on Interix, i.e. seq is still wrong. Can you find out why? Interix has _ before C symbols, all the following are asm symbols. The Interix libc has __vfprintf

eof in nc (netcat)

2007-10-08 Thread Daniel Feenberg
I don't know if this is the right mailing list (nc isn't mentioned in any of the lists) and I don't know if it is a real bug or not, but the GNU version 0.7.1 of nc (the Gnu version of netcat) seems to differ from some other versions of netcat in its treatment of EOF on the standard input.

Re: Fwd: Re: error.c: Unknown system error should report errno value

2007-10-08 Thread Martin Koeppe
Hi Bruno, On Tue, 9 Oct 2007, Bruno Haible wrote: Martin Koeppe wrote: Is seq segfaulting on mingw and BeOS, too? I just tested snapshot 316 and it unfortunately doesn't work on Interix, i.e. seq is still wrong. Can you find out why? Now found out, that GNULIB_SPRINTF_POSIX and

Re: Fwd: Re: error.c: Unknown system error should report errno value

2007-10-08 Thread Bruno Haible
Martin Koeppe wrote: Now found out, that GNULIB_SPRINTF_POSIX and REPLACE_SPRINTF are set to 0 by configure, seems to be the default value, and apparently nowhere else get touched during configure (I only see 2 occurences of these 2 variables in the whole configure), so stay 0 and