WinGrass64-compiling: `libintl_printf' is an unrecognized format function type'

[hellik]

i've compiled the Grass64-releasebranch in the osgeo4w-stack on WinVista32 (--nls enabled).

unfortunately I wasn't all the building time in front of my laptop and couldn't catch all the messages, but I've seen in a few-modules (raster and vector etc.; i.e. nviz, v.what, v.out.pov, v.support, v.transform, v.to.db ) following warnings:

`libintl_printf' is an unrecognized format function type'

compare: ​http://lists.osgeo.org/pipermail/grass-user/2010-January/054025.html

best regards Helmut

[glynn]

Replying to hellik:

unfortunately I wasn't all the building time in front of my laptop and couldn't catch all the messages,

That's why you should redirect output to a file, e.g.

make &> build.log

but I've seen in a few-modules (raster and vector etc.; i.e. nviz, v.what, v.out.pov, v.support, v.transform, v.to.db ) following warnings:

`libintl_printf' is an unrecognized format function type'

I count 77 distinct occurrences (each one will generate multiple warnings, one for each occurrence of __attribute__((format(printf,...))) in gisdefs.h or G3d.h.

Downgrading to "minor", as these are only warnings.

They could be silenced by re-defining attribute to an empty macro (as we do if GNUC isn't defined).

We could eliminate the redirection to libintl_printf, as none of the translations are currently using the %1$ syntax (which the MSVCRT printf() doesn't support, hence the redirection). However, chances are we'll forget to re-instate it if we ever need it.

[hellik]

Replying to glynn:

We could eliminate the redirection to libintl_printf, as none of the translations are currently using the %1$ syntax (which the MSVCRT printf() doesn't support, hence the redirection). However, chances are we'll forget to re-instate it if we ever need it.

so maybe closing as wontfix?

Helmut