HTTPS clone URL
Subversion checkout URL
REL2_0B REL6_4 REL6_5_PATCHES REL7_0_PATCHES REL7_1_STABLE REL7_2_STABLE REL7_3_STABLE REL7_4_STABLE REL8_0_STABLE REL8_1_STABLE REL8_2_STABLE REL8_3_STABLE REL8_4_STABLE REL8_5_ALPHA1_BRANCH REL8_5_ALPHA2_BRANCH REL8_5_ALPHA3_BRANCH REL9_0_ALPHA4_BRANCH REL9_0_ALPHA5_BRANCH REL9_0_STABLE REL9_1_STABLE REL9_2_STABLE REL9_3_STABLE REL9_4_STABLE REL9_5_STABLE Release_1_0_3 WIN32_DEV ecpg_big_bison master
Nothing to show
Nothing to show
Fetching latest commit...
Cannot retrieve the latest commit at this time.
libpgport must have special behavior. It supplies functions to both libraries and applications. However, there are two complexities: 1) Libraries need to use object files that are compiled with exactly the same flags as the library. libpgport might not use the same flags, so it is necessary to recompile the object files for individual libraries. This is done by removing -lpgport from the link line: # Need to recompile any libpgport object files LIBS := $(filter-out -lpgport, $(LIBS)) and adding infrastructure to recompile the object files: OBJS= execute.o typename.o descriptor.o data.o error.o prepare.o memory.o \ connect.o misc.o path.o exec.o \ $(filter snprintf.o, $(LIBOBJS)) The problem is that there is no testing of which object files need to be added, but missing functions usually show up when linking user applications. 2) For applications, we use -lpgport before -lpq, so the static files from libpgport are linked first. This avoids having applications dependent on symbols that are _used_ by libpq, but not intended to be exported by libpq. libpq's libpgport usage changes over time, so such a dependency is a problem. Win32, Linux, and Darwin use an export list to control the symbols exported by libpq.