On Fri, May 9, 2014 at 12:30 AM, Tom Lane wrote:
> Michael Paquier writes:
>> Since commit 60ff2fd introducing the centralizated getopt-related
>> things in a global header file, build on Windows with mingw is failing
>
> Hm, buildfarm member narwhal doesn't seem to be having any such problem.
>
On Fri, May 9, 2014 at 12:55 AM, Andrew Dunstan wrote:
> On 05/08/2014 11:30 AM, Tom Lane wrote:
>> Michael Paquier writes:
>>>
>>> Since commit 60ff2fd introducing the centralizated getopt-related
>>> things in a global header file, build on Windows with mingw is failing
>>
>> Hm, buildfarm memb
On 05/08/2014 11:30 AM, Tom Lane wrote:
Michael Paquier writes:
Since commit 60ff2fd introducing the centralizated getopt-related
things in a global header file, build on Windows with mingw is failing
Hm, buildfarm member narwhal doesn't seem to be having any such problem.
(It's got its own i
Michael Paquier writes:
> Since commit 60ff2fd introducing the centralizated getopt-related
> things in a global header file, build on Windows with mingw is failing
Hm, buildfarm member narwhal doesn't seem to be having any such problem.
(It's got its own issues, but not this.)
Do you think you
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> However, I'm not sure whether 2.5.4 will choke on unrecognized %option
>> commands --- if it has to be conditional on version it'll be a PITA.
> %option noyyget_in
> causes flex 2.5.4a to barf:
On closer investigation, flex does cont
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
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.
Actually, since we don't use any of those functions, the f
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> 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.
Actually, since we don't use any of those functions, the following
advice from
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
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> 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 sa
Andrew Dunstan <[EMAIL PROTECTED]> 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 war
Gregory Stark wrote:
"Tom Lane" <[EMAIL PROTECTED]> writes:
Peter Eisentraut <[EMAIL PROTECTED]> 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. Eve
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Peter Eisentraut <[EMAIL PROTECTED]> 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. W
Peter Eisentraut <[EMAIL PROTECTED]> 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?
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/
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)
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
16 matches
Mail list logo
