Re: ports and printf("%n")

Christian Weisgerber <naddy@mips.inka.de> wrote:

> Jeremie Courreges-Anglas:
>
> > Ports may suffer from this at build time *and* runtime. Regarding
> > issues at build time we can ease the debugging with the diff below.
>
> I've been running with this for months, but nobody asked me for
> results and I didn't push the issue. Grepping /var/log/messages.*
> and deduplicating the results shows this:
>
> devel/bison conftest: *printf used %n: %d %n
> devel/gettext,-runtime conftest: *printf used %n: %d %n
> devel/grcs conftest: *printf used %n: %d %n
> devel/m4 conftest: *printf used %n: %d %n
> editors/poke conftest: *printf used %n: %d %n
> editors/zile conftest: *printf used %n: %d %n
> lang/gpc genmodes: *printf used %n: %s,%n
> lang/gpc genmodes: *printf used %n: %smode,%n
> math/pspp conftest: *printf used %n: %d %n
> net/lftp conftest: *printf used %n: %d %n
> security/gnupg mkdefsinc: *printf used %n: %d %n%s %d
> security/gpgme,-main mkdefsinc: *printf used %n: %d %n%s %d
> sysutils/coreutils conftest: *printf used %n: %d %n
> textproc/groff conftest: *printf used %n: %d %n
> textproc/recutils conftest: *printf used %n: %d %n

Ouch. I was under the impression the %n problem was finished.

Backout required until those get fixed?