On 2012/07/13 02:37, Peter Laufenberg wrote:
I'd just like to point out on-list that we shouldn't be patching
away stpcpy everywhere, it is easy to introduce a bug in perfectly
correct code by doing this (as happened in some cases with strlcpy
patches in the ports tree), it's just that gettext
On 2012/07/13 02:37, Peter Laufenberg wrote:
I'd just like to point out on-list that we shouldn't be patching
away stpcpy everywhere, it is easy to introduce a bug in perfectly
correct code by doing this (as happened in some cases with strlcpy
patches in the ports tree), it's just that gettext
This looks good.
I'd just like to point out on-list that we shouldn't be patching
away stpcpy everywhere, it is easy to introduce a bug in perfectly
correct code by doing this (as happened in some cases with strlcpy
patches in the ports tree), it's just that gettext is *very* commonly
used and
I'd just like to point out on-list that we shouldn't be patching
away stpcpy everywhere, it is easy to introduce a bug in perfectly
correct code by doing this (as happened in some cases with strlcpy
patches in the ports tree), it's just that gettext is *very* commonly
used and the linker warning
The goal here is to get rid of these warnings that fill our build
logs:
/usr/local/lib/libintl.so.6.0: warning: stpcpy() is dangerous GNU crap; don't
use it
Note that this is only about libintl proper, not about the msg*
tools and their helper libraries.
These patches need reviewing. I'm not
