From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, gorm(dot)andersen(at)sun(dot)com, books(at)ejurka(dot)com |
Subject: | Re: compiler warnings on the buildfarm |
Date: | 2007-07-13 00:19:04 |
Message-ID: | 16415.1184285944@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> animal: dragonfly warnings: 67
> auth.c:61: warning: initialization from incompatible pointer type
> animal: emperor_moth warnings: 10
> auth.c:61: warning: initialization from incompatible pointer type
Apparently, Solaris 9 and 10 have funny ideas about the signature of the
PAM callback function. We have
static int pam_passwd_conv_proc(int num_msg, const struct pam_message ** msg,
struct pam_response ** resp, void *appdata_ptr);
which exactly matches what my Fedora 6 pam header file says it should
be. What is it on those Solaris machines? (Look for struct pam_conv
in the headers)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2007-07-13 00:25:58 | Re: compiler warnings on the buildfarm |
Previous Message | Tom Lane | 2007-07-12 23:51:10 | pgsql: Fix a portability bug (ye olde not casting a <ctype.h> argument |