Paul Eggert wrote:
> On 10/02/2012 02:03 PM, Simon Josefsson wrote:
>> I have a use for the inttostr module in a library inside OATH Toolkit
>> that will be released under LGPLv2+.
>
> Sure, that's fine with me.
That is fine with me, too.
On 10/02/2012 12:31 PM, Eric Blake wrote:
> POSIX left errno undefined on ptsname() failure, although there
> has at least been an effort to specify reasonable values to use:
> http://www.austingroupbugs.net/view.php?id=503
>
> However, our tests for ptsname and ptsname_r already require errno
> t
Similar to the recent select fixes.
* doc/posix-functions/pselect.texi (pselect): Document this.
* m4/pselect.m4 (gl_FUNC_PSELECT): Probe for FreeBSD bug.
* lib/pselect.c (rpl_pselect) [!win32]: Work around it.
* modules/pselect (Depends-on): Add dup2.
---
ChangeLog| 6 ++
On 10/02/2012 02:03 PM, Simon Josefsson wrote:
> I have a use for the inttostr module in a library inside OATH Toolkit
> that will be released under LGPLv2+.
Sure, that's fine with me.
POSIX requires invalid file descriptors to be detected rather than
silently ignored. FreeBSD 8.2 detects if fd 0 has been closed
and appears in a set while fd 1 is still open, but mistakenly
optimizes and refuses to check any fds in the set beyond the
maximum open fd.
* doc/posix-functions/select
On 10/02/2012 03:03 PM, Simon Josefsson wrote:
> Paul, Jim,
>
> I have a use for the inttostr module in a library inside OATH Toolkit
> that will be released under LGPLv2+. The inttostr module is currently
> licensed as LGPL. Would it be possible to relicense it to LGPLv2+? Its
> dependencies a
Paul, Jim,
I have a use for the inttostr module in a library inside OATH Toolkit
that will be released under LGPLv2+. The inttostr module is currently
licensed as LGPL. Would it be possible to relicense it to LGPLv2+? Its
dependencies appears to be LGPLv2+ already, so it should only be matter
o
POSIX left errno undefined on ptsname() failure, although there
has at least been an effort to specify reasonable values to use:
http://www.austingroupbugs.net/view.php?id=503
However, our tests for ptsname and ptsname_r already require errno
to be set to useful values (as in glibc), so it is wort
On 10/02/2012 10:46 AM, Ed Maste wrote:
> On 2 October 2012 10:30, Ed Maste wrote:
>
>> Thanks for the list - here's the current status, on 9.1 prerelease.
>> It'll take a little while to fully analyze the remaining failures.
>
> Here are some additional details and a re-sorted list.
>
> *** Al
On 2 October 2012 10:30, Ed Maste wrote:
> Thanks for the list - here's the current status, on 9.1 prerelease.
> It'll take a little while to fully analyze the remaining failures.
Here are some additional details and a re-sorted list.
*** Already fixed or in progress:
>> fcntl
>> This function
On 09/06/2012 03:42 PM, Eric Blake wrote:
> Some versions of gcc (at least 4.2.1) noisily warn if
> -Wuninitialized is given without -O; in isolation, configure
> learns that the warning option is supported, but when later
> compiling with -Werror, this makes builds fail. If the
> option will have
Nikos Mavrogiannopoulos wrote:
> On Mon, Oct 1, 2012 at 8:46 PM, Jim Meyering wrote:
>
>>> Any update on that? Do you plan to include it?
>> I went to deal with the mechanics of adding it and noticed a few details.
>> What do you think about hash_pjw_no_mod or hash_pjw_bare
>> as the function nam
On 1 October 2012 22:50, Bruno Haible wrote:
> Hi Ed,
>
>> it looks like we're pretty close to having all of
>> the tests apply and pass on FreeBSD so I suspect I don't have many
>> more to find.
>
> Do you know what is the status of the following bugs in the newest
> FreeBSD release? Let me cite
On 10/01/2012 12:00 AM, Bruno Haible wrote:
> [Dropping bug-coreutils from CC]
>
> Hi Stefano,
>
Hi Bruno, sorry for the late answer.
>> OK, this is a minor annoyance rather than a real bug, but I guess
>> reporting it won't hurt.
>>
>> In GNU coreutils, the gnulib-provided 'bootstrap' script fai
On Mon, Oct 1, 2012 at 8:46 PM, Jim Meyering wrote:
>> Any update on that? Do you plan to include it?
> I went to deal with the mechanics of adding it and noticed a few details.
> What do you think about hash_pjw_no_mod or hash_pjw_bare
> as the function name? They convey more meaning than the
15 matches
Mail list logo