Re: new snapshot available: sed-4.2.2.189-2439

[Jim Meyering]

On Tue, Dec 20, 2016 at 8:16 PM, Assaf Gordon <address@hidden> wrote:
>>  http://meyering.net/sed/sed-4.2.2.189-2439.tar.xz
>
> only few minor test failures, most of them are gnulib related and were 
> discussed elsewhere (e.g. coreutils).

Thanks for all that testing.
Glad to hear there's nothing sed-specific, so far.

> On NetBSD 7.0.1, gnulib's "test-localename" fails to link (undefined ref to 
> 'uselocale').
> On AIX-7, gnulib's "test-localename" fails (exit code 132).
> With musl-libc on Ubuntu 14.04, gnulib's "test-localename" and 
> "test-mbrtowc5" fail.
>
> One strange thing is that with clang-3.9 and clang-4.0 (from Ubuntu's 
> backports):
> the build fails with "undefined reference to '__muloti4'".

My guess is that this is unrelated to sed.

> Perhaps it's a problem with my system - I haven't investigated further yet.
> A brief search shows mentions of this as an llvm bug:
>  https://llvm.org/bugs/show_bug.cgi?id=16404
>
> ===== build error with clang ====
> $ make
> [....]
> CC       lib/obstack.o
> lib/obstack.c:351:31: warning: incompatible pointer types initializing 'void 
> (*)(void) __attribute__((noreturn))' with an expression of type 'void (void)' 
> [-Wincompatible-pointer-types]
> __attribute_noreturn__ void (*obstack_alloc_failed_handler) (void)
> ^

IMHO, none of this should hold up a sed release.