Re: peripatus build failures....

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Larry Rosenman <ler@lerctr.org>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2018-07-07T15:24:48Z
Lists: pgsql-hackers
Larry Rosenman <ler@lerctr.org> writes:
> On Sat, Jul 07, 2018 at 11:11:24AM -0400, Tom Lane wrote:
>> Larry Rosenman <ler@lerctr.org> writes:
>>> f044d71e331d77a0039cec0a11859b5a3c72bc95 fixed it.

>> Don't think I believe that conclusion; that patch shouldn't
>> have affected anything at all for non-ARM architectures.

> Those are the 2 adjacent commits in src/port.

You're assuming something not in evidence, which is that the critical
change was textually within src/port/.  It might have been in configure,
for instance, or in Makefile.global, or some other upper-level makefile.
I'd just do a straight bisect run without any assumptions about which part
of the tree matters.

			regards, tom lane


Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Prevent accidental linking of system-supplied copies of libpq.so etc.

  2. Fix partial-build problems introduced by having more generated headers.

  3. Fix the new ARMv8 CRC code for short and unaligned input.

  4. Use ARMv8 CRC instructions where available.

  5. Fix incorrect description of USE_SLICING_BY_8_CRC32C.

  6. Add an assertion that we don't pass NULL to snprintf("%s").

  7. Update copyright for 2018