Mart Somermaa <[EMAIL PROTECTED]> writes:
> - the implementation is simple, effective and 2^n/10^n-problem agnostic
> (at the cost of comparing 10K less than 1M, which is not a problem
> as we assume the input to be properly scaled).
That's the cost that I'm worried about. The input is not a
Hi Sam,
* Sam Sirlin wrote on Wed, May 31, 2006 at 01:11:49AM CEST:
>From: Ralf Wildenhues <[EMAIL PROTECTED]>
>Is your script home-grown or does it have some wider usage? What does
>it output upon
> dirname -- /
>
> It's old code from SVr2, so it may be lurking around on old s
Date: Tue, 30 May 2006 07:24:31 +0200
From: Ralf Wildenhues <[EMAIL PROTECTED]>
* Sam Sirlin wrote on Mon, May 29, 2006 at 10:41:03PM CEST:
>From: Ralf Wildenhues <[EMAIL PROTECTED]>
> /bin/bash --version
> echo $PATH
> type mkdir expr dirname basename
On Tue, May 30, 2006 at 10:27:48PM +0200, Bruno Haible wrote:
> Ralf Wildenhues wrote:
> > > Hmm? My results for AIX 5.1 differ: On AIX 5.1.0.0 I get
> > >
> > > checking whether strndup is declared... yes
> > > checking for working strndup... no
> > > checking whether strnlen is declared... yes
>
On Sun, May 28, 2006 at 05:52:45PM +0200, Ralf Wildenhues wrote:
>
> ... AIX strndup is severely broken, at least on 4.3.3 and 5.1, similar
> to its strnlen; see also[1]. See for example this test:
>
> $ cat >a.c <<\EOF
> #include
> #include
>
> extern char *strndup (const char *, size_t);
>
On Tue, May 30, 2006 at 09:48:24PM +0200, Ralf Wildenhues wrote:
> * Bruno Haible wrote on Tue, May 30, 2006 at 09:29:37PM CEST:
> > Ralf Wildenhues wrote:
> > > Tested on AIX 4.3.3, 5.1, 5.2 (first has strnlen and strndup broken,
> > > second has strnlen fixed, last has both fixed)
> >
> > Hmm? M
Ralf Wildenhues wrote:
> > Hmm? My results for AIX 5.1 differ: On AIX 5.1.0.0 I get
> >
> > checking whether strndup is declared... yes
> > checking for working strndup... no
> > checking whether strnlen is declared... yes
> > checking for working strnlen... no
>
> (lslpp -L). The one I tested on
* Bruno Haible wrote on Tue, May 30, 2006 at 09:29:37PM CEST:
> Ralf Wildenhues wrote:
> > Tested on AIX 4.3.3, 5.1, 5.2 (first has strnlen and strndup broken,
> > second has strnlen fixed, last has both fixed)
>
> Hmm? My results for AIX 5.1 differ: On AIX 5.1.0.0 I get
>
> checking whether strn
Hi Bruno,
* Bruno Haible wrote on Tue, May 30, 2006 at 09:11:04PM CEST:
>
> I added your patch to gnulib, with 4 modifications:
Thanks for applying, your modifications are all good.
> > + test $gl_cv_func_strndup = no &&
> > + if test $gl_cv_func_strndup = no; then
>
> Was this intended redu
Ralf Wildenhues wrote:
> Tested on AIX 4.3.3, 5.1, 5.2 (first has strnlen and strndup broken,
> second has strnlen fixed, last has both fixed)
Hmm? My results for AIX 5.1 differ: On AIX 5.1.0.0 I get
checking whether strndup is declared... yes
checking for working strndup... no
checking whether s
Ralf Wildenhues wrote:
> Not sure if I have much motivation for fighting this into glibc, but
> here you go. I'm unsure if conditionalizing away the #undef __strndup
> is wrong for some system.
>
> Tested on AIX 4.3.3, 5.1, 5.2 (first has strnlen and strndup broken,
> second has strnlen fixed, las
On Tue, May 30, 2006 at 11:25:14AM +0200, Jim Meyering wrote:
> Albert Chin <[EMAIL PROTECTED]> wrote:
> > On Sun, May 28, 2006 at 07:58:24PM +0200, Jim Meyering wrote:
> >> I have to confess that I wonder if it's worth trying to work around
> >> bugs in AIX 4. Is it still officially supported? I
Paul Eggert wrote:
> Mart Somermaa <[EMAIL PROTECTED]> writes:
>
>
>> What is the general consensus on adding the '--human-readable-bytesize'
>> otpion to sort?
>>
>
> A problem with it is figuring out how to add lots of options to sort.
> We're running out of letters. This one probably do
Albert Chin <[EMAIL PROTECTED]> wrote:
> On Sun, May 28, 2006 at 07:58:24PM +0200, Jim Meyering wrote:
>> I have to confess that I wonder if it's worth trying to work around
>> bugs in AIX 4. Is it still officially supported? Is it used by many?
>> I haven't had access to such a system for a few
Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> I get 3 failures on hppa2.0w-hp-hpux11.23:
Regarding this one,
> misc/close-stdout
it's because HP-UX's exec-family functions are not POSIX conforming.
As described in http://www.opengroup.org/susv3xsh/execl.html, calling
exec* with one or more of the
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> (I assume you meant "... >&- 2>/dev/null".)
Yes, thanks. Actually, the "2>/dev/null" can be omitted.
> Seems "fclose (stdout)" isn't returning an error in this case.
Ouch. I suppose one possibility is a bug in the HP-UX C library.
Another is tha
Hi Paul,
* Paul Eggert wrote on Tue, May 30, 2006 at 09:51:17AM CEST:
> Thanks for reporting this. All these failures seem to be due to a
> portability problem in lib/closeout.c. Could you please run, say, "cp
> --verbose /dev/null /tmp/foo >&- >/dev/null" in a debugger, putting a
> breakpoint o
Mart Somermaa <[EMAIL PROTECTED]> writes:
> What is the general consensus on adding the '--human-readable-bytesize'
> otpion to sort?
A problem with it is figuring out how to add lots of options to sort.
We're running out of letters. This one probably doesn't deserve a
single letter. And yet si
Thanks for reporting this. All these failures seem to be due to a
portability problem in lib/closeout.c. Could you please run, say, "cp
--verbose /dev/null /tmp/foo >&- >/dev/null" in a debugger, putting a
breakpoint on the close_stdout function, and see why it isn't calling
'error' with a nonzer
19 matches
Mail list logo
