From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Meskes <meskes(at)postgresql(dot)org> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: minor compiler warning on OpenBSD |
Date: | 2007-07-16 16:02:18 |
Message-ID: | 15163.1184601738@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Meskes <meskes(at)postgresql(dot)org> writes:
> On Wed, Jul 11, 2007 at 07:18:17PM -0400, Tom Lane wrote:
>> Now if we could only get rid of those flex-induced warnings in ecpg...
> Don't you get the same in the backend's parser code? I surely do.
No, ecpg is the only one producing warnings for me. What flex version
do you use?
> It seems these are only missing prototypes. How about adding an include
> file with those prototypes?
What I get with flex 2.5.4 is
pgc.c: In function `base_yylex':
pgc.c:1564: warning: label `find_rule' defined but not used
preproc.y: At top level:
pgc.c:3818: warning: `yy_flex_realloc' defined but not used
neither of which seem fixable that way.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-07-16 16:04:41 | Re: Straightforward changes for increased SMP scalability |
Previous Message | Andrew Dunstan | 2007-07-16 15:48:27 | Re: Straightforward changes for increased SMP scalability |