Re: compiler warnings on the buildfarm

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, Kris Jurka <books(at)ejurka(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Gorm(dot)Andersen(at)Sun(dot)COM
Subject: Re: compiler warnings on the buildfarm
Date: 2007-07-13 13:52:10
Message-ID: 20908.1184334730@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> Zdenek Kotala wrote:
>> I don't see any "const" keyword there.

> Right after that:

>> where int conv(int num_msg, const struct pam_message **msg, struct pam_response **resp, void *appdata_ptr);

> How confusing...

And the pam_start page he cited earlier has a different set of typos in
its version of the struct :-(. Still, that's two out of three places
that say it's const, and Solaris appears to be the only implementation
that has chosen to read it as not const.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2007-07-13 13:58:17 Re: compiler warnings on the buildfarm
Previous Message Hannu Krosing 2007-07-13 13:50:56 has anyone looked at burstsort ?