Files
postgres/src/port
Tom Lane c43feefa80 Add erand48() to the set of functions supported by our src/port/ library,
and extend configure to test for it properly instead of hard-wiring
an assumption that everybody but Windows has the rand48 functions.
(We do cheat to the extent of assuming that probing for erand48 will do
for the entire rand48 family.)

erand48() is unused as of this commit, but a followon patch will cause
GEQO to depend on it.

Andres Freund, additional hacking by Tom
2009-07-16 17:43:52 +00:00
..
2009-02-10 19:29:39 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2008-03-21 13:23:29 +00:00
2003-11-29 19:52:15 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-01 17:24:05 +00:00
2009-01-14 21:18:30 +00:00
2009-01-01 17:24:05 +00:00
2004-10-07 13:59:45 +00:00
2009-01-01 17:24:05 +00:00
2009-07-01 23:15:55 +00:00

$PostgreSQL: pgsql/src/port/README,v 1.4 2008/03/21 13:23:29 momjian Exp $

libpgport
=========

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.