Re: pgsql: Move gramparse.h to src/backend/parser

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: "Anton A(dot) Melnikov" <a(dot)melnikov(at)postgrespro(dot)ru>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Move gramparse.h to src/backend/parser
Date: 2025-10-16 04:19:36
Message-ID: CANWCAZaCk6mX1c4oCQc9fzjtiVZ_Fh19dipOScy7XEjJqAd3gg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Oct 15, 2025 at 2:49 PM Anton A. Melnikov
<a(dot)melnikov(at)postgrespro(dot)ru> wrote:
> My colleague Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru> found
> the similar bug on buildfarm [1] for REL_15_STABLE in the llvm build:
>
> -D_GNU_SOURCE -I/usr/include/libxml2 -flto=thin -emit-llvm -c -o segparse.bc segparse.c
> segparse.y:177:10: fatal error: 'segscan.c' file not found
> 177 | #include "segscan.c"
> | ^~~~~~~~~~~
> 1 error generated
>
> Maybe backpatch [2] to all supported versions not just 16+?

That only changed src/backend/common.mk, so that's not going to affect
contrib. I looked, and contrib/contrib-global.mk doesn't have any
extra *.bc file handling to begin with (as expected). Also, that fix
was in response to a specific change in dependencies, so I don't see
how it's directly applicable to earlier branches. Maybe there is
something to be done here, but with such a sporadic failure, I'm not
sure what.

--
John Naylor
Amazon Web Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2025-10-16 04:34:51 Re: pgsql: Move gramparse.h to src/backend/parser
Previous Message Michael Paquier 2025-10-16 02:40:44 pgsql: Override log_error_verbosity to "default" in test 009_log_temp_f