Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rPlqr-00E1FX-9R for pgsql-bugs@arkaria.postgresql.org; Tue, 16 Jan 2024 15:59:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rPlqq-004p6K-9T for pgsql-bugs@arkaria.postgresql.org; Tue, 16 Jan 2024 15:59:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rPlqp-004p68-TB for pgsql-bugs@lists.postgresql.org; Tue, 16 Jan 2024 15:59:44 +0000 Received: from mail-pg1-x52e.google.com ([2607:f8b0:4864:20::52e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rPlqn-0028g6-3P for pgsql-bugs@lists.postgresql.org; Tue, 16 Jan 2024 15:59:43 +0000 Received: by mail-pg1-x52e.google.com with SMTP id 41be03b00d2f7-5ca1b4809b5so4163584a12.3 for ; Tue, 16 Jan 2024 07:59:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ardentperf-com.20230601.gappssmtp.com; s=20230601; t=1705420779; x=1706025579; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=w+miB2kcoqoPJ6fUSihmV0yX95AZYtxpRNVg3kOteKg=; b=n//1x2inV2Es13eNvc941KhAVo/vs5aJYi+jCDFEB5xAGgv9EvGZmI1MbaTMoCP8hg yWck0cwE9v0DSr0Z18pCKpBOxeTiSk1Ou4gHCGx/3Jt1cRdtV8vn3jpB2iqBOlGur7l4 QTUNO+UxHxe18TCo/8JsD2KvoaufEQ4gfEEYg9ySSFbBxAkuMrT4vyph2M8wFzaTVfJt yz1yI1czo47QJc+XqeXnO8vsVfJB8E9uWV3D/Mwz4QHKThk3ko9azjLPZcHVUhQAw2+6 NmF8Rmh76OisoGFgMEwvYUOyOenYOhk/0UDFhfEbDyBkBLidF+TY0M2leYo5Ekuwou7Y IYRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705420779; x=1706025579; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=w+miB2kcoqoPJ6fUSihmV0yX95AZYtxpRNVg3kOteKg=; b=w0MplC7gh6BcaM2IsuZoaHH7I3rFI+Yo9YqFP2z4UJrB4w+AuhNYnWI2/ugdKeFjuQ t7cBZKHNeApL007fDuq1DhfpDLVoMqJVdz5QH1yhQeqb0EPz98ZJk875cac8s2asKsVB a+Wr0h3Gd2ccDy0zIE+ztqXveJYMfQQs7biDnvauKKcaJE6aQbyAclvAGY7bO5BQBXa8 xedTzx90g5EG+R1Maupyol40WF9JuErkR+fHcc3UY0fCZE2AGdz1/tOaWmP8RJ5wiXPy LiOjvQRInfjYyHohjs72yk0gSEAQHWmMiv7QfwZOC0BXoveRkCntCRy2IlLHd4JWhBaf u/wQ== X-Gm-Message-State: AOJu0YyaIScgq8nvc593KCIQNgC/EwJ7RT2C02qLSSWguszCuHBlnuxK BYYoI3b26cDVWg6AY58DsMZzOnRn2CHG X-Google-Smtp-Source: AGHT+IGEO0/2MN2QiUnxxNZzoUK+hMGhP6VGPOzSUWhBxfbWA783vv50+9/eOvpSOYQ00l51I2+Qvw== X-Received: by 2002:a05:6a20:4394:b0:19a:eb8c:3dce with SMTP id i20-20020a056a20439400b0019aeb8c3dcemr2615160pzl.120.1705420778759; Tue, 16 Jan 2024 07:59:38 -0800 (PST) Received: from [10.88.149.175] ([205.251.233.107]) by smtp.gmail.com with ESMTPSA id fa38-20020a056a002d2600b006d99125b114sm9470524pfb.65.2024.01.16.07.59.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Jan 2024 07:59:38 -0800 (PST) Message-ID: <0635f417-41fa-4d3a-af2d-781c8c68d7ad@ardentperf.com> Date: Tue, 16 Jan 2024 07:59:36 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global To: =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= , Thomas Munro , john.fensterman@charter.com, pgsql-bugs@lists.postgresql.org References: <18289-cc1b88346b51af93@postgresql.org> Content-Language: en-US From: Jeremy Schneider In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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