Does anyone happen to know what it is about my build environment that causes
these errors? I get a similar slew of errors from each flex lexer we built
including the plpgsql lexer, the ecpg lexer, etc. Do I have the wrong version
of flex installed? Something else? It's quite annoying, especially as the beta
version of Emacs I'm using seems to not be able to parse these lines.

In file included from gram.y:9493:
scan.c:7050: warning: no previous prototype for 'base_yyget_lineno'
scan.c:7059: warning: no previous prototype for 'base_yyget_in'
scan.c:7067: warning: no previous prototype for 'base_yyget_out'
scan.c:7075: warning: no previous prototype for 'base_yyget_leng'
scan.c:7084: warning: no previous prototype for 'base_yyget_text'
scan.c:7093: warning: no previous prototype for 'base_yyset_lineno'
scan.c:7105: warning: no previous prototype for 'base_yyset_in'
scan.c:7110: warning: no previous prototype for 'base_yyset_out'
scan.c:7115: warning: no previous prototype for 'base_yyget_debug'
scan.c:7120: warning: no previous prototype for 'base_yyset_debug'
scan.c:7154: warning: no previous prototype for 'base_yylex_destroy'


--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Gregory Stark wrote:
> Does anyone happen to know what it is about my build environment that causes
> these errors? I get a similar slew of errors from each flex lexer we built
> including the plpgsql lexer, the ecpg lexer, etc. Do I have the wrong version
> of flex installed? Something else? It's quite annoying, especially as the beta
> version of Emacs I'm using seems to not be able to parse these lines.
>
> In file included from gram.y:9493:
> scan.c:7050: warning: no previous prototype for 'base_yyget_lineno'
>
>
[snip]

What versions of flex and bison are you using? It's a bit hard to
diagnose without knowing that ;-)

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Am Mittwoch, 28. Februar 2007 16:23 schrieb Gregory Stark:
> Does anyone happen to know what it is about my build environment that
> causes these errors?

Nothing. Everybody gets them.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Peter Eisentraut wrote:
> Am Mittwoch, 28. Februar 2007 16:23 schrieb Gregory Stark:
>
>> Does anyone happen to know what it is about my build environment that
>> causes these errors?
>>
>
> Nothing. Everybody gets them.
>
>

That's not what the buildfarm shows.

example:
http://www.pgbuildfarm.org/cgi-bin/s...13002&stg=make

cheers

andrew


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Peter Eisentraut <peter_e@gmx.net> writes:
> Am Mittwoch, 28. Februar 2007 16:23 schrieb Gregory Stark:
>> Does anyone happen to know what it is about my build environment that
>> causes these errors?

> Nothing. Everybody gets them.

I don't. What version of flex are you guys using?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> Peter Eisentraut <peter_e@gmx.net> writes:
>> Am Mittwoch, 28. Februar 2007 16:23 schrieb Gregory Stark:
>>> Does anyone happen to know what it is about my build environment that
>>> causes these errors?
>
>> Nothing. Everybody gets them.
>
> I don't. What version of flex are you guys using?

flex 2.5.33

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Gregory Stark wrote:
> "Tom Lane" <tgl@sss.pgh.pa.us> writes:
>
>
>> Peter Eisentraut <peter_e@gmx.net> writes:
>>
>>> Am Mittwoch, 28. Februar 2007 16:23 schrieb Gregory Stark:
>>>
>>>> Does anyone happen to know what it is about my build environment that
>>>> causes these errors?
>>>>
>>> Nothing. Everybody gets them.
>>>
>> I don't. What version of flex are you guys using?
>>
>
> flex 2.5.33
>
>

Aha! Known to be broken, iirc. Use flex 2.5.4a

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Andrew Dunstan <andrew@dunslane.net> writes:
> Gregory Stark wrote:
>> flex 2.5.33

> Aha! Known to be broken, iirc. Use flex 2.5.4a

No, the known breakages with flex were years ago; 2.5.33 has only been
out a year. I think 2.5.31 might have been the one we saw big problems
with (there's a note warning against using it on the flex sourceforge
page).

I think most of us do still use 2.5.4a, but it'd probably be a good idea
to check out 2.5.33 and see if it can be made to not generate warnings.
I'm certainly tired of seeing the warnings 2.5.4a creates ...

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>
>> Gregory Stark wrote:
>>
>>> flex 2.5.33
>>>
>
>
>> Aha! Known to be broken, iirc. Use flex 2.5.4a
>>
>
> No, the known breakages with flex were years ago; 2.5.33 has only been
> out a year. I think 2.5.31 might have been the one we saw big problems
> with (there's a note warning against using it on the flex sourceforge
> page).
>
> I think most of us do still use 2.5.4a, but it'd probably be a good idea
> to check out 2.5.33 and see if it can be made to not generate warnings.
> I'm certainly tired of seeing the warnings 2.5.4a creates ...
>



It gives me the same warnings that Greg reported.

I guess we could conditionally add prototypes for those functions to all
the .l files if you really want to move to 2.5.33. Kinda yucky, though.

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

I wrote:
>
>
> I guess we could conditionally add prototypes for those functions to
> all the .l files if you really want to move to 2.5.33. Kinda yucky,
> though.
>
>

Actually, we couldn't.The definition section from the .l file gets
included after these functions. So we'd need to include something in
gram.y before including scan.c.

cheers

andrew


---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate