| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: win_flex.exe (and likely win_bison.exe) isn't concurrency safe |
| Date: | 2022-09-03 05:21:51 |
| Message-ID: | 20220903052151.ck5oytvhspfqkyrw@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)anarazel(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2022-09-03 05:30:03 | warning: comparison of integer expressions of different signedness related to simd.h |
| Previous Message | Amit Kapila | 2022-09-03 05:03:43 | Re: win_flex.exe (and likely win_bison.exe) isn't concurrency safe |