Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global

From: Devrim Gündüz <devrim(at)gunduz(dot)org>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, john(dot)fensterman(at)charter(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
Date: 2024-01-15 15:23:21
Message-ID: e83f61cee7f2c8cfdac51327a4faa356fbea8c70.camel@gunduz.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Sat, 2024-01-13 at 17:33 +1300, Thomas Munro wrote:
>
> Now if the package maintainer

:)

> 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?

Cheers,
--
Devrim Gündüz
Open Source Solution Architect, PostgreSQL Major Contributor
Twitter: @DevrimGunduz , @DevrimGunduzTR

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dmitry Koval 2024-01-15 15:47:17 Re: BUG #18274: Error 'invalid XML content'
Previous Message Hayato Kuroda (Fujitsu) 2024-01-15 12:58:08 RE: Re:Re: BUG #18267: Logical replication bug: data is not synchronized after Alter Publication.