Re: fix: propagate M4 env variable to flex subprocess

From: Andres Freund <andres(at)anarazel(dot)de>
To: "J(dot) Javier Maestro" <jjmaestro(at)ieee(dot)org>
Cc: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: fix: propagate M4 env variable to flex subprocess
Date: 2025-05-28 17:08:46
Message-ID: ot4w2y6es446gjgvhbpp45qt3wx65n5epjxgsu3ghgr63yuizn@qeurkcofswmv
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2025-05-17 23:32:24 -0400, J. Javier Maestro wrote:
> On Tue, May 13, 2025 at 11:54 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > Bilal, I think you wrote this originally, do you recall?
> >
> > It seems like an issue beyond just M4...
> >
>
> IIRC the rest of the tools in the environment have ways to be specified via
> Meson options (BISON, FLEX, PERL) so the only issue I see is Flex not being
> able to find the specific m4 binary. What other issue(s) are you
> considering?

PATH, LD_LIBRARY_PATH, ...

I think this really should just add to the environment, rather than supplant
it. Do you want to write a patch like that? Otherwise I can.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shubhankar Anand Kulkarni 2025-05-28 18:23:46 Re: Expression push down from Join Node to below node.
Previous Message Andres Freund 2025-05-28 17:02:22 Re: wrong query results on bf leafhopper