From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | "J(dot) Javier Maestro" <jjmaestro(at)ieee(dot)org>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: fix: propagate M4 env variable to flex subprocess |
Date: | 2025-05-13 15:54:42 |
Message-ID: | 2p2here7um2uymvq2rdl2z6ljmfm4qduoquexmuj5y4bclmjju@umygr75jv6cp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2025-05-12 23:14:59 -0400, J. Javier Maestro wrote:
> The pgflex wrapper runs flex with an explicit environment, so it doesn't
> inherit environment variables from the parent process. However, flex can
> use the M4 env variable and/or the PATH (via execvp) to find the m4 macro
> processor.
> Thus, since flex honors the M4 env variable, it should be propagated to the
> subprocess environment if it's set in the parent environment. This patch
> fixes it.
I think it probably was not intentional to fully specify the environment,
rather than just *adding* FLEX_TMP_DIR to the caller's environment. Bilal, I
think you wrote this originally, do you recall?
It seems like an issue beyond just M4...
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Yura Sokolov | 2025-05-13 16:22:29 | ARM/ARM64 SpinLockAcquire and SpinLockRelease are not full barriers |
Previous Message | Andres Freund | 2025-05-13 15:25:21 | spurious pg_amcheck test failure |