public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jason Petersen <[email protected]>
To: [email protected]
Subject: enable-rpath in Red Hat builds
Date: Wed, 8 Jun 2016 15:12:20 -0600
Message-ID: <[email protected]> (raw)
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-pkg-yum>
I hadn’t noticed until recently that --enable-rpath is passed to configure on Red Hat PostgreSQL builds and inherited by all extensions (via pg_config) on that platform. rpmlint complains about it on several Red Hat variants (well, in fact it _errors_).
Poking around mailing lists and git history, I was able to ascertain that it wasn’t always this way, with some caveats around how plperl and plpython are build on these platforms.
Does anyone have a pointer as to why this was changed for PostgreSQL itself? Or when?
Do extensions need to worry about this? I see some that use e.g. chrpath on binaries, but without understanding the reason PostgreSQL itself uses an rpath-enabled build I didn’t want to add that.
Planning on just filtering this rpmlint error for now, but I am curious for the motivation.
--
Jason Petersen
Software Engineer | Citus Data
303.736.9255
[email protected]
Attachments:
[application/pgp-signature] signature.asc (496B, 3-signature.asc)
download
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: enable-rpath in Red Hat builds
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox