On Mon, Jul 16, 2007 at 06:09:47PM +0200, Stefan Kaltenbrunner wrote:
> I think Michael is refering to:
>
> In file included from bootparse.y:380:
> bootscanner.c:1855: warning: no previous prototype for
> ‘boot_yyget_lineno’
> ...
Right, I was talking about these messages.
Michael
--
Micha
On Mon, Jul 16, 2007 at 12:02:18PM -0400, Tom Lane wrote:
> No, ecpg is the only one producing warnings for me. What flex version
> do you use?
2.5.33
> 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:
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> 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
>>
>>
Tom Lane wrote:
Michael Meskes <[EMAIL PROTECTED]> 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 w
Michael Meskes <[EMAIL PROTECTED]> 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.
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.
It seems these are only missing prototypes. How about adding an include
file with those prototypes?
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> My local manpage for strftime says that we can get around this warning
>> by overloading it with something like
>
>> size_t
>> my_strftime(char *s, size_t max, const char *fmt,
>> const struct tm *tm)
>> {
>> return strf
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> My local manpage for strftime says that we can get around this warning
> by overloading it with something like
> size_t
> my_strftime(char *s, size_t max, const char *fmt,
> const struct tm *tm)
> {
> return strftime(s, max, fmt, tm);
>
Stefan Kaltenbrunner wrote:
> Tom Lane wrote:
> > Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> >> while looking at some other stuff I noticed that we have the following
> >> compiler warning on OpenBSD 4.0/amd64 with the OS supplied compiler:
> >> initdb.c:2187: warning: `%x' yields only last
Tom Lane wrote:
> Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
>> while looking at some other stuff I noticed that we have the following
>> compiler warning on OpenBSD 4.0/amd64 with the OS supplied compiler:
>> initdb.c:2187: warning: `%x' yields only last 2 digits of year in some
>> locales
>
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> while looking at some other stuff I noticed that we have the following
> compiler warning on OpenBSD 4.0/amd64 with the OS supplied compiler:
> initdb.c:2187: warning: `%x' yields only last 2 digits of year in some
> locales
Yeah, mine complains a
while looking at some other stuff I noticed that we have the following
compiler warning on OpenBSD 4.0/amd64 with the OS supplied compiler:
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline
-Wendif-labels -fno-strict-aliasing -DFRONTEND
-I../../../src/interfaces/libpq -I../../../src/incl
12 matches
Mail list logo
