Hi Paul,
Thanks for the quick response.
On 9 Mar 2013, at 00:04, Paul Eggert <egg...@cs.ucla.edu> wrote:
> On 03/08/2013 08:43 AM, Gary V. Vaughan wrote:
>> Anything else I can do to help fix this?
>
> Can you tell us what my_asprintf is putting into 'result'?
If I print result just before the failing assert, stdout has this extra line:
0x1p+0 33
Going over the build logs, I also noticed this warning when compiling
test-xvasprintf.c,
which is likely entirely unrelated -- my original report being
test-xvasprintf-posix.c
failing.
CC test-xvasprintf.o
../../tests/test-xvasprintf.c: In function 'test_xasprintf':
../../tests/test-xvasprintf.c:98: warning: format not a string literal and no
format arguments
CCLD test-xvasprintf
> To be honest, though, this test shouldn't matter for M4,
> so perhaps you should just disable it.
Agreed, but it would be nicer still if all Mac OS using gnulib clients didn't
have to
work around the failure :)
Cheers,
--
Gary V. Vaughan (gary AT gnu DOT org)
