pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeremy Schneider <schneider@ardentperf.com>
To: Devrim Gündüz <devrim@gunduz.org>
To: Thomas Munro <thomas.munro@gmail.com>
To: john.fensterman@charter.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
Date: Tue, 16 Jan 2024 07:59:36 -0800
Message-ID: <0635f417-41fa-4d3a-af2d-781c8c68d7ad@ardentperf.com> (raw)
In-Reply-To: <e83f61cee7f2c8cfdac51327a4faa356fbea8c70.camel@gunduz.org>
References: <18289-cc1b88346b51af93@postgresql.org>
	<CA+hUKGK2HG4ZdBfVHuT6kUnUcy-bBZZWM_QifE-pYEQFMyPtPA@mail.gmail.com>
	<e83f61cee7f2c8cfdac51327a4faa356fbea8c70.camel@gunduz.org>

On 1/15/24 7:23 AM, Devrim Gündüz wrote:
>> used a different major version of clang than you're using to compile
>> your extension, it may have some compiler flags that your compiler
>> doesn't like.  I guess that problem is more general than LLVM, though?
> 
> Hmm, so does it mean that I need to rebuild (almost) every extension
> that has llvmjit subpackage each time when RHEL releases a new LLVM
> version? 

I've been chatting w John over slack about this too, not closely
involved but I've been trying to be helpful if I can

My understanding is that the problem is with PGXS and the
temporal_tables extension, which is not already-built & available as an RPM.

I'd think we wouldn't need to rebuild extensions that are available as
RPMs. Isn't the problem basically that PGXS preserves all the compiler
settings in Makefile.global that were used to build Postgres on the
build machine, and that someone who builds an extension later might not
have a matching environment to that Postgres RPM build environment?

While it's far from ideal, I think the right short-term workaround for
John is to manually edit Makefile.global to remove the problematic clang
flags and hopefully this doesn't "void the warranty" when he builds the
temporal tables extension, right?

(I assume temporal_tables is not available as a pre-built RPM)

-Jeremy


-- 
http://about.me/jeremy_schneider






view thread (10+ messages)  latest in thread

Message-ID: <0635f417-41fa-4d3a-af2d-781c8c68d7ad@ardentperf.com>
Permalink:  ../0635f417-41fa-4d3a-af2d-781c8c68d7ad@ardentperf.com/
Also on:    postgresql.org/message-id/0635f417-41fa-4d3a-af2d-781c8c68d7ad@ardentperf.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: schneider@ardentperf.com, devrim@gunduz.org, thomas.munro@gmail.com, john.fensterman@charter.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
  In-Reply-To: <0635f417-41fa-4d3a-af2d-781c8c68d7ad@ardentperf.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox