Tom Lane dddfc4cb2e Prevent accidental linking of system-supplied copies of libpq.so etc. ... We were being careless in some places about the order of -L switches in link command lines, such that -L switches referring to external directories could come before those referring to directories within the build tree. This made it possible to accidentally link a system-supplied library, for example /usr/lib/libpq.so, in place of the one built in the build tree. Hilarity ensued, the more so the older the system-supplied library is. To fix, break LDFLAGS into two parts, a sub-variable LDFLAGS_INTERNAL and the main LDFLAGS variable, both of which are "recursively expanded" so that they can be incrementally adjusted by different makefiles. Establish a policy that -L switches for directories in the build tree must always be added to LDFLAGS_INTERNAL, while -L switches for external directories must always be added to LDFLAGS. This is sufficient to ensure a safe search order. For simplicity, we typically also put -l switches for the respective libraries into those same variables. (Traditional make usage would have us put -l switches into LIBS, but cleaning that up is a project for another day, as there's no clear need for it.) This turns out to also require separating SHLIB_LINK into two variables, SHLIB_LINK and SHLIB_LINK_INTERNAL, with a similar rule about which switches go into which variable. And likewise for PG_LIBS. Although this change might appear to affect external users of pgxs.mk, I think it doesn't; they shouldn't have any need to touch the _INTERNAL variables. In passing, tweak src/common/Makefile so that the value of CPPFLAGS recorded in pg_config lacks "-DFRONTEND" and the recorded value of LDFLAGS lacks "-L../../../src/common". Both of those things are mistakes, apparently introduced during prior code rearrangements, as old versions of pg_config don't print them. In general we don't want anything that's specific to the src/common subdirectory to appear in those outputs. This is certainly a bug fix, but in view of the lack of field complaints, I'm unsure whether it's worth the risk of back-patching. In any case it seems wise to see what the buildfarm makes of it first. Discussion: https://postgr.es/m/25214.1522604295@sss.pgh.pa.us		2018-04-03 16:26:05 -04:00
..
autoinc--1.0.sql
autoinc--unpackaged--1.0.sql
autoinc.c	Use wrappers of PG_DETOAST_DATUM_PACKED() more.	2017-03-12 19:35:34 -04:00
autoinc.control
autoinc.example
insert_username--1.0.sql
insert_username--unpackaged--1.0.sql
insert_username.c
insert_username.control
insert_username.example
Makefile	Prevent accidental linking of system-supplied copies of libpq.so etc.	2018-04-03 16:26:05 -04:00
moddatetime--1.0.sql
moddatetime--unpackaged--1.0.sql
moddatetime.c	Generate fmgr prototypes automatically	2017-01-17 14:06:07 -05:00
moddatetime.control
moddatetime.example
refint--1.0.sql
refint--unpackaged--1.0.sql
refint.c	Remove dead assignment	2018-01-29 20:41:36 -05:00
refint.control
refint.example
timetravel--1.0.sql
timetravel--unpackaged--1.0.sql
timetravel.c	Document and use SPI_result_code_string()	2017-10-04 22:14:21 -04:00
timetravel.control
timetravel.example