Paul Eggert wrote in
<https://lists.gnu.org/archive/html/coreutils/2025-09/msg00111.html>:
> While we're on the subject of bogus OpenBSD warnings, perhaps we should
> do something about OpenBSD's style nattering. Linker warnings like this:
>
> warning: strcpy() is almost always misused, please use strlcpy()
>
> are a waste of time for us, and we can fix them in Gnulib by defining
> our own strcpy that overrides OpenBSD's.
There are many functions like strcpy(), that produce such warnings in
OpenBSD (and some also on macOS). Fixing this by overriding strcpy() et al.
is going to be quite intrusive. Possibly also causing trouble in shared
libraries.
I'd prefer either
* to ignore the problem. The user who builds the package can filter
the warnings:
grep warning: build.log | grep -v misused | grep -v dangerous
or
* to eliminate these warnings through the 'compile' wrapper that we
already use for some platforms (native Windows for example).
Similarly in the 'macos-compile' wrapper.
This is much less intrusive.
Bruno
