Re: win_flex.exe (and likely win_bison.exe) isn't concurrency safe - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: win_flex.exe (and likely win_bison.exe) isn't concurrency safe
Date
Msg-id 20220903052151.ck5oytvhspfqkyrw@jrouhaud
Whole thread Raw
In response to Re: win_flex.exe (and likely win_bison.exe) isn't concurrency safe  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Sat, Sep 03, 2022 at 10:33:43AM +0530, Amit Kapila wrote:
> On Sat, Sep 3, 2022 at 4:13 AM Andres Freund <andres@anarazel.de> wrote:
> > For the meson build it is trivial to "address" this by setting FLEX_TMP_DIR to
> > a private directory (which we already need to deal with lex.backup), something
> > similar could be done for src/tools/msvc.
> >
> >
> > Unless we think it'd be better to just refuse to work with winflexbison?
> >
> 
> Personally, I have never used this but I feel it would be good to keep
> it working especially if others are using it.

My windows environments rely on winflexbison so I'd prefer if we keep the
compatibility (or improve it).  I personally never hit that problem, but I
don't work much on Windows either.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: win_flex.exe (and likely win_bison.exe) isn't concurrency safe
Next
From: Pavel Stehule
Date:
Subject: warning: comparison of integer expressions of different signedness related to simd.h