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-06T22:40:49Z
Lists: pgsql-hackers
Larry Rosenman <ler@lerctr.org> writes:
> anyone want to look at this, or at least give me a clue on how to add
> this to 10 & below?

I do not like the "-Wl,-z,notext" thing at all.  It fails to explain
why things are working OK in v11/HEAD, which makes me think that it's
band-aiding something rather than really fixing it.

Perhaps you could spend a bit of time with git bisect and find out
which commit un-broke things?  That should help us narrow down the
true explanation.

			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