diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-07-09 17:23:31 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-07-09 17:23:31 -0400 |
commit | c74f48a4ec54c36b515f85a6b779a4751b7070b7 (patch) | |
tree | 28221d10f99d0b922cfe23496b7e9eddaf1b42f9 /src/tutorial/complex.c | |
parent | b0da7ecad332244364152ff6f00fd0ceb8733781 (diff) | |
download | postgresql-c74f48a4ec54c36b515f85a6b779a4751b7070b7.tar.gz postgresql-c74f48a4ec54c36b515f85a6b779a4751b7070b7.zip |
Prevent accidental linking of system-supplied copies of libpq.so etc.
Back-patch commit dddfc4cb2, which broke LDFLAGS and related Makefile
variables into two parts, one for within-build-tree library references and
one for external libraries, to ensure that the order of -L flags has all
of the former before all of the latter. This turns out to fix a problem
recently noted on buildfarm member peripatus, that we attempted to
incorporate code from libpgport.a into a shared library. That will fail on
platforms that are sticky about putting non-PIC code into shared libraries.
(It's quite surprising we hadn't seen such failures before, since the code
in question has been like that for a long time.)
I think that peripatus' problem could have been fixed with just a subset
of this patch; but since the previous issue of accidentally linking to the
wrong copy of a Postgres shlib seems likely to bite people in the field,
let's just back-patch the whole change. Now that commit dddfc4cb2 has
survived some beta testing, I'm less afraid to back-patch it than I was
at the time.
This also fixes undesired inclusion of "-DFRONTEND" in pg_config's CPPFLAGS
output (in 9.6 and up) and undesired inclusion of "-L../../src/common" in
its LDFLAGS output (in all supported branches).
Back-patch to v10 and older branches; this is already in v11.
Discussion: https://postgr.es/m/20180704234304.bq2dxispefl65odz@ler-imac.local
Diffstat (limited to 'src/tutorial/complex.c')
0 files changed, 0 insertions, 0 deletions