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>
Subject: Re: compile warnings in CVS HEAD?
Date: 2003-09-04 02:30:05
Message-ID: 3501.1062642605@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'm seeing the following with the current CVS code on my Linux dev box:

> In file included from bootparse.y:340:
> lex.Int_yy.c:1832: warning: no previous prototype for `Int_yyget_lineno'
> lex.Int_yy.c:1841: warning: no previous prototype for `Int_yyget_in'
> ...etc...

These are flex's fault. AFAICT flex 2.5.31 is a long way short of being
production quality. I recommend reverting to 2.5.4.

> tablecmds.c: In function `validateForeignKeyConstraint':
> tablecmds.c:3546: warning: dereferencing type-punned pointer will break
> strict-aliasing rules

Hm. Got any idea what these are really complaining about? I see no
such gripes with the gcc versions I use, but I wouldn't be surprised
if gcc 3.3 is trying to tighten up.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2003-09-04 02:40:11 Re: Using oids
Previous Message Tom Lane 2003-09-04 02:24:51 Re: Transaction status in default psql prompt?