Re: localization problem (and solution)

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <andreas+pg(at)gate450(dot)dyndns(dot)org>, <masm(at)fciencias(dot)unam(dot)mx>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: localization problem (and solution)
Date: 2005-12-29 17:21:47
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

Tom Lane said:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> I would also like to add -Wno-comment to the CFLAGS for win32/gcc, top
>> suppress at least some of those warnings.
> Why don't you complain to the Perl people, instead? The fact that no
> such warnings occur on Unix Perl installations makes these seem pretty
> suspicious.

Well, it's probably not even the Perl people - perl's config_h.SH seems to
do the right thing and put a space between the second / and *, so that the
compiler won't complain, so it could be ActiveState's doing. Maybe I'll just
make a tiny script to fix config.h in my perl distro.

There is a more serious problem, though, in these warnings. Perl is
apparently trying to hijack the *printf functions, just as libintl tries to
do. There's a #define we can set to inhibit that, and I think we should.
That would leave 2 lots of warnings to fix - one about uid_t/gid_t and one
about isnan.



In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-12-29 17:30:49 Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
Previous Message Greg Stark 2005-12-29 17:20:32 Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and