Re: peripatus build failures....

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Larry Rosenman <ler(at)lerctr(dot)org>
Cc: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: peripatus build failures....
Date: 2018-07-07 18:28:17
Message-ID: 71057.1530988097@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Larry Rosenman <ler(at)lerctr(dot)org> writes:
> And the winner is:

> dddfc4cb2edcfa5497f5d50190a7fb046c51da16 is the first bad commit
> commit dddfc4cb2edcfa5497f5d50190a7fb046c51da16
> Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2018-07-07 18:33:26 Re: peripatus build failures....
Previous Message Jeff Janes 2018-07-07 18:07:55 Re: Make deparsing of column defaults faster