From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mathew Heard <mat999@gmail.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18839: ARMv7 builds fail due to missing __crc32cw and
 similar
In-reply-to: 
 <CAE5sJtSzqXVNzCdU1P+2YYSZ2yO4ceN11wUmZg5-gAGSrnwEWw@mail.gmail.com>
References: 
 <CAE5sJtTG7ZTZqPHW003AuLEi6yO8vqY04vVXx5jZbPt1FRViXQ@mail.gmail.com>
 <2953389.1741911582@sss.pgh.pa.us>
 <CAE5sJtSzqXVNzCdU1P+2YYSZ2yO4ceN11wUmZg5-gAGSrnwEWw@mail.gmail.com>
Comments: In-reply-to Mathew Heard <mat999@gmail.com>
	message dated "Fri, 14 Mar 2025 11:51:22 +1100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2958436.1741914536.1@sss.pgh.pa.us>
Date: Thu, 13 Mar 2025 21:08:56 -0400
Message-ID: <2958437.1741914536@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2958437.1741914536%40sss.pgh.pa.us>
Precedence: bulk

Mathew Heard <mat999@gmail.com> writes:
> If I am correct, postgresql is identifying the CPU of the build system as
> ARMv8 in that test, and using this rather than the target architecture.

The configure script isn't "identifying" anything.  It's just seeing
whether references to __crc32cb() etc will compile with different
-march flags.  It's not apparent why a successful test of that sort
would not lead to a successful compilation with the same flags later
on.  We might do a *run time* probe of the actual CPU type, but that
has nothing to do with compilation.

You still haven't told us which -march setting configure is selecting,
nor provided the config.log trace showing why it chose that one.
You also haven't described the compilation environment in any detail
--- eg, I still am not sure if this is a hard-float or soft-float
environment.

			regards, tom lane