Re: compile warnings in CVS HEAD

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Michael Meskes <meskes(at)postgresql(dot)org>
Subject: Re: compile warnings in CVS HEAD
Date: 2003-04-14 03:10:33
Message-ID: 1365.1050289833@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Neil Conway <neilc(at)samurai(dot)com> writes:
> I get the following warnings when compiling CVS HEAD:

> be-secure.c: In function `open_server_SSL':
> be-secure.c:719: warning: assignment from incompatible pointer type

I saw someone else report this too, but it doesn't happen on my
machines. Could you look into it and see just what the issue is?

> timestamp.c: In function `dttofmtasc_replace':
> timestamp.c:468: warning: `%g' yields only last 2 digits of year
> timestamp.c:606: warning: `%x' yields only last 2 digits of year in some
> locales

The recently-added ecpg library files exhibit half a dozen warnings on
my boxen. I'm not sure whether Michael is ready to worry about
portability issues for that stuff yet. I'm happy to cut him some slack
if he's not worried yet --- but agreed, I don't want to still be seeing
these messages when we approach release. Michael, what's your take?

regards, tom lane

PS: I think Michael just left on vacation, so we may not get an answer
for a couple weeks ...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-04-14 03:37:40 Re: Anyone working on better transaction locking?
Previous Message cbbrowne 2003-04-14 01:37:56 Re: PostgreSQL on a Cluster