| 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 15:24:48 |
| Message-ID: | 70759.1530977088@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:
> On Sat, Jul 07, 2018 at 11:11:24AM -0400, Tom Lane wrote:
>> Larry Rosenman <ler(at)lerctr(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2018-07-07 16:05:00 | Re: peripatus build failures.... |
| Previous Message | Larry Rosenman | 2018-07-07 15:20:51 | Re: peripatus build failures.... |