Hi Paul, > > my patch from 2025-05-28 > > https://lists.gnu.org/archive/html/bug-gnulib/2025-05/msg00266.html > > Oh, it seems that coreutils doesn't have that fix yet. I reverted the > Gnulib openat-die patches.
Thanks. > > 2) Do we care about random warnings on non-GNU systems? > > Not usually, no. I thought this might be an exception but obviously I > was mistaken. I think the warning-avoiding fix in gettext.h works only for gcc, because gcc recognizes 'gettext', 'dgettext', 'dcgettext' as built-ins. IIRC, clang doesn't, so there is no way currently to do the same fix with clang. *IF* we want clang to be as warning-free as gcc, in this case, we should report it as a feature request to the LLVM people. But the more pragmatic way is to just accept the fact that clang produces more warnings than gcc, and to filter out / triage the warnings from the compilation log. Btw, for this triaging I use the attached script (works with both gcc and clang). Bruno
warnings-by-category
Description: application/shellscript
