Re: Setting rpath on llvmjit.so?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Yuriy Zhuravlev <stalkerg(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Setting rpath on llvmjit.so?
Date: 2018-04-18 14:57:38
Message-ID: 31484.1524063458@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> On 4/17/18 16:14, Andres Freund wrote:
>> I still think cmake is the least unreasonable path going forward.

> I would rather try to make Meson work and if needed add features back
> into Meson.

I'm wondering whether that will result in expending a lot of effort
to move from a poorly-supported build system to a different
poorly-supported build system. As a project, we have an astonishingly
poor track record for choosing outside projects to rely on :-(.

One thing I particularly dislike about Meson, after reading its wikipedia
entry for a moment, is that it doesn't use "make" as the backend build
system. That means two major tooling changes not one, and double the
opportunity to find ourselves stuck with unsupported infrastructure.
I also politely decline the offer to be forced to use XCode on mac.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-04-18 15:01:56 Re: pruning disabled for array, enum, record, range type partition keys
Previous Message Robert Haas 2018-04-18 14:57:26 Re: Setting rpath on llvmjit.so?