This problem came up for Libidn but it seems to be a problem with the
update-copyright self check, it fails under Cygwin.
> * Cygwin 1.7.9
>
> Fails already in the gnulib tests:
>
> 1 of 36 tests failed
>
> --- - 2011-11-23 01:13:33.194375000 +0100
> +++ update-copyright.test-ex-stderr 2011-11-2
Simon Josefsson wrote:
> This problem came up for Libidn but it seems to be a problem with the
> update-copyright self check, it fails under Cygwin.
>
>> * Cygwin 1.7.9
>>
>> Fails already in the gnulib tests:
>>
>> 1 of 36 tests failed
>>
>> --- -2011-11-23 01:13:33.194375000 +0100
>> +++
Jim Meyering writes:
> Hi Simon,
> It looks like somehow perl is being run with -pi.bak.
>
> However, here's a patch that should avoid that:
Thank you! I'll re-enable the self-test in libidn and proceed with the
release process...
>> test-update-copyright.sh that creates them, so I suspect tha
Simon Josefsson writes:
> Jim Meyering writes:
>
>> Hi Simon,
>> It looks like somehow perl is being run with -pi.bak.
>>
>> However, here's a patch that should avoid that:
>
> Thank you! I'll re-enable the self-test in libidn and proceed with the
> release process...
I noticed the patch hasn'
Simon Josefsson wrote:
> Jim Meyering writes:
>
>> Hi Simon,
>> It looks like somehow perl is being run with -pi.bak.
>>
>> However, here's a patch that should avoid that:
>
> Thank you! I'll re-enable the self-test in libidn and proceed with the
> release process...
Pushed.
>>> test-update-cop
This also came up for Libidn, it is using the latest gnulib.
> * mingw with gcc
>
> Fails already in the gnulib tests:
>
> FAIL: test-binary-io.sh
I have not seen this test fail before. Bruno, I noticed you had written
that self-test, could you add some printf's at various places (or single
step
[adding bug-gnulib; replies can drop libvirt]
On 11/25/2011 05:51 AM, Paolo Bonzini wrote:
>> Indeed; Linux has posix_memalign, and mingw never runs the io helper
>> (although it does compile it, hence the #if). If gnulib would give
>> us posix_memalign on mingw, we could nuke this #if altogether
[Cc bug-gnulib/gettext/standards/texinfo, Bcc gnu-prog-discuss]
On 11/25/2011 02:51 PM, Thien-Thi Nguyen wrote:
GNU programs are urged to use `symbol' (grave, symbol, apostrophe)
in README, Texinfo uses those to implement @code in Info files, etc.
I propose GNU adopt U+2018 symbol U+2019 instea
On 11/25/2011 07:38 AM, Eric Blake wrote:
[adding bug-gnulib; replies can drop libvirt]
Providing a posix_memalign_free defeats the purpose - POSIX requires
that plain free() will cover the memory returned by posix_memalign. The
list of platforms missing posix_memalign is a bit daunting:
Mac
Jim Meyering wrote:
> It looks like somehow perl is being run with -pi.bak.
Yes, apparently this is the cause. The .bak suffix appears to be the default.
I have not specified it through environment variables.
$ ls -l foo3*
-rw-r--r-- 1 bruno Kein 73 Nov 25 21:46 foo3.c
$ perl -pi -e s/x/x/ foo3.
[Dropping libvir-list]
Eric Blake wrote:
> >> If gnulib would give
> >> us posix_memalign on mingw, we could nuke this #if altogether.
> >
> > That's pretty difficult (unless you also add a posix_memalign_free)
> > because at the time posix_memalign returns you have lost the base
> > pointer for
[Dropping libvir-list]
Peter O'Gorman wrote:
> Many of these systems have valloc(3) which could be used for this purpose.
Yes, but gnulib's pagealign_alloc() function is less wasteful that the
valloc() function that some systems have. E.g. in OpenBSD:
void *
valloc(size_t i)
{
long valsi
12 matches
Mail list logo
