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-07T18:28:17Z
Lists: pgsql-hackers
Larry Rosenman <ler@lerctr.org> writes:
> And the winner is:

> dddfc4cb2edcfa5497f5d50190a7fb046c51da16 is the first bad commit
> commit dddfc4cb2edcfa5497f5d50190a7fb046c51da16
> Author: Tom Lane <tgl@sss.pgh.pa.us>
> Date:   Tue Apr 3 16:26:05 2018 -0400
>
>     Prevent accidental linking of system-supplied copies of libpq.so etc.

Huh.  So what that suggests is that the problem is related to picking
up copies of our libraries from outside the build tree.  Do you have
any copies of libpgport.a/.so or libpgcommon.a/.so in
/usr/local/lib or /usr/lib or /lib ?

			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