Hello Bruno, Bruno Haible <br...@clisp.org> writes:
> This problem comes from gnulib and was recently fixed in gnulib [1][2][3]. > > Since new glibc versions get rolled out to millions of systems, I think > it would be good to have a new libunistring release quickly. > > Bruno > > [1] > https://lists.gnu.org/archive/html/bug-gnulib/2018-03/msg00000.html > [2] > http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=4af4a4a71827c0bc5e0ec67af23edef4f15cee8e > [3] > http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=74d9d6a293d7462dea8f83e7fc5ac792e956a0ad Although I agree that this build issue affects many systems, I am not sure if this is worth an immediate new release, because: - these days, most people install this library as a distribution package, in particular if they are using glibc based systems - since the above fixes only touch *.[ch] files, distributions could easily patch their packages without bootstrapping So, my preference is to deliver it as part of potentially significant run-time changes, such as synching with Unicode 10. I wouldn't oppose if you handle the release ;-) Regards, -- Daiki Ueno
