Re: fix: propagate M4 env variable to flex subprocess - Mailing list pgsql-hackers

From Andres Freund
Subject Re: fix: propagate M4 env variable to flex subprocess
Date
Msg-id 2p2here7um2uymvq2rdl2z6ljmfm4qduoquexmuj5y4bclmjju@umygr75jv6cp
Whole thread Raw
List 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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Add partial :-variable expansion to psql \copy
Next
From: Salvatore Dipietro
Date:
Subject: Re: Remove Instruction Synchronization Barrier in spin_delay() for ARM64 architecture