OK this is the other bug (i was just about to write something about being out of sync heh). Soo, first of all this has been fixed since we're using a different system to create the translations now, but furthermore I would like to point out that the code that produced the warningns (the code in the intl/ directory IIRC) is/was not part of BMP, so fixing this on _our_ side by removing the -std=c99 argument would, if you want to put it on the sharp edge, constitute a workaround and i'd rather propagate this further upstream so that either they (GNU i guess erm, yeah GNU intltool) state that their code isn't C99 compliant (which would be a little problematic for the case that your app contains C99 code), or they fix it to _be_ C99 compliant but in either case i don't see why BMPx should remove a build flag which is perfectly valid for its own code.
Regards, Milosz On 12/4/06, dann frazier <[EMAIL PROTECTED]> wrote:
Is there any other explanation you need to upload a fix? The problem is that the CFLAGS are telling the compiler to restrict itself to a standard that does not include the strdup definition, so the obvious solution is to stop doing that: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398253;msg=7;att=0 -- dann frazier
