On 2018-12-19 09:15, Hagen Paul Pfeifer wrote: > > On December 19, 2018 at 2:44 AM Matthias Klose <d...@debian.org> wrote: > > > > this is unrelated to GCC, but happens with glibc 2.28. > > Thank you Matthias! It happens with the "visual" gcc update, sry for that. > > glibc folks: do you need any more information? Should I test/verify > anything?
No, we do not need more information the problem is known, and is on the gnulib side. It uses glibc internal defines, and therefore breaks when internal things changes. A patch has been committed upstream back in March, but hasn't propagated yet to all projects having an embedded copy: http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a71827c0bc5e0ec67af23edef4f15cee8e It is not perfect has it replaces one internal define by another, but should do the trick for now. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
