Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bAkm8-0004ia-MI for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 08 Jun 2016 21:12:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bAkm7-0003aG-M5 for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 08 Jun 2016 21:12:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bAkm4-0003Wl-5k for pgsql-pkg-yum@postgresql.org; Wed, 08 Jun 2016 21:12:28 +0000 Received: from mail-oi0-x229.google.com ([2607:f8b0:4003:c06::229]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bAkm0-0004Sg-PS for pgsql-pkg-yum@postgresql.org; Wed, 08 Jun 2016 21:12:27 +0000 Received: by mail-oi0-x229.google.com with SMTP id p204so33287539oih.3 for ; Wed, 08 Jun 2016 14:12:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=citusdata.com; s=google; h=from:subject:date:message-id:to:mime-version; bh=2RPLtat8i6+DXs5klQ5um11S7gqJBz9T8Cn6bK+LC9g=; b=THjCWkGcdYiKPphq6KXVwyYRU3Dev006ioZ027ttjf6gQeESZrQI3pid12gxUKT4sd ColU0O/0PIQ6kVc+oxNt+YAFn0mG9utL+qNa8Q+RYXN6zZdZaFpfoRtkYr0BK1SBFmgr WaMYi9pSW8JyzjkumAoYr6JAHIWf0fISdSga4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:date:message-id:to:mime-version; bh=2RPLtat8i6+DXs5klQ5um11S7gqJBz9T8Cn6bK+LC9g=; b=VQCpRmMXG36kokAYCRsI7e3XlpoTZWYPJqhFF+mxGVsgvrKxeYIRfGbsFPJ0JrlfIq /LdAMGkPYXpaEPuh6bXdYs/kcgqfa838bDWOS47uIAHhl6MD9cIVVhl8Q55BvVYcGMr6 HbpG0tilwBzLPIgR9V2H/2B2ISPJbWLVaB3qhDAa/NjOLvERRYhgdtstuhlOgeC27AOn 5Ii4RFzsXa7BCgXm+YTrEyKnyKJKtcV1KWCdHmVDCn675bLJD+/g79DXIdD7qy51rhhI tIMxtEWub22fYJEyhuNpSX/HMzdG+yjhcvFhFICHEGhRTW5yDWHU9BOpRvPwtML5eFXK WNVg== X-Gm-Message-State: ALyK8tIiAJ4UYUV0vk+3+z3eYqBvzfG+x+/hvNuCy5Q+4uKVahtm837SLKEosJ6GVom12E52 X-Received: by 10.202.183.213 with SMTP id h204mr4170863oif.26.1465420342433; Wed, 08 Jun 2016 14:12:22 -0700 (PDT) Received: from [10.62.5.133] ([63.76.231.82]) by smtp.gmail.com with ESMTPSA id h10sm1314805otb.35.2016.06.08.14.12.21 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 08 Jun 2016 14:12:21 -0700 (PDT) From: Jason Petersen X-Pgp-Agent: GPGMail Content-Type: multipart/signed; boundary="Apple-Mail=_656117BB-1BA1-4E36-91F6-ABCD11045F41"; protocol="application/pgp-signature"; micalg=pgp-sha512 Subject: enable-rpath in Red Hat builds Date: Wed, 8 Jun 2016 15:12:20 -0600 Message-Id: To: pgsql-pkg-yum@postgresql.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-pkg-yum Precedence: bulk Sender: pgsql-pkg-yum-owner@postgresql.org --Apple-Mail=_656117BB-1BA1-4E36-91F6-ABCD11045F41 Content-Type: multipart/alternative; boundary="Apple-Mail=_5E2D93D9-4DF0-4646-88E5-BFCECA2ACA30" --Apple-Mail=_5E2D93D9-4DF0-4646-88E5-BFCECA2ACA30 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I hadn=E2=80=99t 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=E2=80=99t 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=E2=80=99t 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 jason@citusdata.com --Apple-Mail=_5E2D93D9-4DF0-4646-88E5-BFCECA2ACA30 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I hadn=E2=80=99t 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=E2=80=99t = 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=E2=80=99t 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

= --Apple-Mail=_5E2D93D9-4DF0-4646-88E5-BFCECA2ACA30-- --Apple-Mail=_656117BB-1BA1-4E36-91F6-ABCD11045F41 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJXWIo0AAoJEJ8dNRDREKupRigH/2su+b69xYeSAJeKhKC7pNIK ipNpVznlB36JLsHUmgVdElbMhzurUiirNHKMRIztlgInM4/cgxLLPhmQgguYVjgj UOUfJyzfqI0302dTFbhpDQjiKEaveBG9StSRgmvy31RehyANyLeIOn7np6SweHMz Q3fBzAfAMzS2RsAh2BVVoiFEXsuoDHT8g2qr3jxPvd9o/aodccamo3q9kzBT59YZ nbW/wNr2qbSwl4wPcXcViWR5GXgGkz0LOTZJVsa6b+eryayKKBPgGnuIzaE3Xpxd 8KhflRICCIEENpO/KWfs+d543EmjdLWuxGF15NCk5bOp9pG6gCFy2Lj0ZlOAGcE= =1Oqx -----END PGP SIGNATURE----- --Apple-Mail=_656117BB-1BA1-4E36-91F6-ABCD11045F41--