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 1tssmC-006Piq-Mk for pgsql-bugs@arkaria.postgresql.org; Fri, 14 Mar 2025 00:19:48 +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 1tssmB-009d7R-DB for pgsql-bugs@arkaria.postgresql.org; Fri, 14 Mar 2025 00:19:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tssmB-009d7J-4V for pgsql-bugs@lists.postgresql.org; Fri, 14 Mar 2025 00:19:47 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tssm9-002hWX-12 for pgsql-bugs@lists.postgresql.org; Fri, 14 Mar 2025 00:19:46 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 52E0JgIn2953390; Thu, 13 Mar 2025 20:19:42 -0400 From: Tom Lane To: Mathew Heard cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18839: ARMv7 builds fail due to missing __crc32cw and similar In-reply-to: References: Comments: In-reply-to Mathew Heard message dated "Thu, 13 Mar 2025 13:09:53 +1100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2953388.1741911582.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 13 Mar 2025 20:19:42 -0400 Message-ID: <2953389.1741911582@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Mathew Heard writes: > The relevant commit we have removed from our build that has returned the > ability to build is. > https://github.com/postgres/postgres/commit/5980f1884fc911af120c98ad440b= 9546ed9012c5 > GCC 12.2.0-3 (latest for debian bullseye) > Debian Bullseye > ARMv7 (Allwinner H3) I spent some time today trying to reproduce this, without success. One thing I noticed is that Debian 11 seems to have shipped with gcc 10.2.1, while gcc 12.2.0 comes with Debian 12 (Bookworm). I don't doubt that you can get gcc 12 for Debian 11, but I wonder if there's some OS-vs-compiler version skew underlying this issue for you. The real question though is how the configure test could succeed only to get a failure in the main build. If you would get "undefined reference to `__crc32cb'" etc in the main build, the configure probe should have failed in the same way. I tried assorted -march settings with both of those gcc versions and it acted as-expected for me. regards, tom lane