Bruno Haible writes:
> Hi Simon,
>
>> While debugging a 'asprintf' bug on Windows, I noticed that building the
>> 'vasprintf' module fails:
>>
>> gnulib-tool --create-testdir --dir m --with-tests vasprintf
>> cd m
>> ./configure --host=i586-mingw32msvc --build=i686-pc-linux-gnu
>> make
>>
>> r
Hi Simon,
> While debugging a 'asprintf' bug on Windows, I noticed that building the
> 'vasprintf' module fails:
>
> gnulib-tool --create-testdir --dir m --with-tests vasprintf
> cd m
> ./configure --host=i586-mingw32msvc --build=i686-pc-linux-gnu
> make
>
> results in:
>
> g++ -DHAVE_CONFIG_H
Bruno Haible writes:
> Simon Josefsson wrote:
>> HAVE_OPENPTY is not set in config.h though -- isn't that a bug? The
>> system has openpty.
>> ...
>> Single stepping rpl_openpty:
>>
>> master = open ("/dev/ptmx", O_RDWR | O_NOCTTY);
>> if (master < 0)
>> => return -1;
>>
>> And indeed my
Eric Blake writes:
> On 04/21/2010 05:21 AM, Simon Josefsson wrote:
>> For some reason 'asprintf (&tmp, "%08lx", 1)' yields '61fdec3039'.
>> I haven't started debugging the printf code yet, but will get to it...
>
> Is this on a 32-bit or 64-bit platform? It matters if you are asking to
> pr
On 04/21/2010 05:21 AM, Simon Josefsson wrote:
> For some reason 'asprintf (&tmp, "%08lx", 1)' yields '61fdec3039'.
> I haven't started debugging the printf code yet, but will get to it...
Is this on a 32-bit or 64-bit platform? It matters if you are asking to
print a 64-bit long, but passed
Dagobert Michelsen writes:
> Hi Simon,
>
> Am 31.03.2009 um 12:23 schrieb Simon Josefsson:
>> Dagobert Michelsen writes:
>>> I am getting a test failure on Solaris 8 Sparc w/Sun Studio 11:
>>
>> Hi! Thanks for the report. The problem is actually in a self-test
>> from
>> gnulib. Your GNU SASL
I've pushed the patch below since it demonstrates a bug in gnulib's
printf code under Windows.
gnulib-tool --create-testdir --avoid string-c++-tests --dir m --with-tests
vasprintf
cd m
./configure --host=i586-mingw32msvc --build=i686-pc-linux-gnu
make check
For some reason 'asprintf (&tmp, "%08l
While debugging a 'asprintf' bug on Windows, I noticed that building the
'vasprintf' module fails:
gnulib-tool --create-testdir --dir m --with-tests vasprintf
cd m
./configure --host=i586-mingw32msvc --build=i686-pc-linux-gnu
make
results in:
g++ -DHAVE_CONFIG_H -I. -DGNULIB_STRICT_CHECKING=1
Hi Chen,
> I mailed my signature off a good month ago, it should be. Bruno,
> did you get anything from the FSF yet?
No, I didn't get a notification from the FSF so far, and the copyright.list
on FSF machines (which was last modified yesterday) does not contain your
name either, today.
I guess w
On Mon, Feb 01, 2010 at 08:58:19AM +0100, Jim Meyering wrote:
> Bruno Haible wrote:
> > Jim Meyering wrote:
> >> Imagine that the first 10 tests pass, then each of the remaining ones is
> >> killed via e.g., SIGHUP. ...
> >> a naive search for "FAIL:" in the build output would find nothing.
> >
> >
Hi Padraig,
> From: Pádraig Brady
> To: Bruno Haible
> Cc: Chen Guo ; bug-gnulib@gnu.org
> Sent: Wed, April 21, 2010 1:46:47 AM
> Subject: Re: [PATCH] (x)memcoll: performance improvement when input is known
> to be NUL delimited.
>
> On 14/03/10 14:24, Bruno Haible wrote:
> Hi Chen,
>
>> ..
On 14/03/10 14:24, Bruno Haible wrote:
> Hi Chen,
>
>> ... it was consistently (as in every run for 20 runs) faster, and thus I've
>> included it in the patch.
>
> Thanks. I'll wait for the FSF notification that the legal papers have arrived.
Hi Chen, The copyright stuff is sorted now I presume
[sorry Joel for not replying to all initially]
> > Or have gnulib's getopt.h explicitly define __STDC__ to 1?
>
> Will that work for every getopt.h that gnulib's getopt.h might include?
> It seems that, in practice, the use of __STDC__ is not very standard.
Having OpenCSW regenerate the libgnuget
13 matches
Mail list logo
