of course, I meant --as-needed rather than --as-necessary
Andrew Dunstan wrote:
Dennis Bjorklund wrote:
This is the output in Fedora Core 2, and it includes readline:
$ ldd /usr/bin/postgres
linux-gate.so.1 => (0x0024)
libpam.so.0 => /lib/libpam.so.0 (0x00cf1000)
libssl.s
Dennis Bjorklund wrote:
This is the output in Fedora Core 2, and it includes readline:
$ ldd /usr/bin/postgres
linux-gate.so.1 => (0x0024)
libpam.so.0 => /lib/libpam.so.0 (0x00cf1000)
libssl.so.4 => /lib/libssl.so.4 (0x0014e000)
libcrypto.so.4 => /lib/libcrypto.so.
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I am confused. I just checked my backend binary and I don't see any
> unusual libs required:
> $ ldd postgres
> libz.so => /usr/lib/libz.so (0x2833f000)
> libncurses.so.5 => /shlib/libncurses.so.5 (0x2834e000)
I do not believe eit
On Sat, 25 Sep 2004, Bruce Momjian wrote:
> I am confused. I just checked my backend binary and I don't see any
> unusual libs required:
>
> $ ldd postgres
> libz.so => /usr/lib/libz.so (0x2833f000)
> libncurses.so.5 => /shlib/libncurses.so.5 (0x2834e000)
> libdl.so
I am confused. I just checked my backend binary and I don't see any
unusual libs required:
$ ldd postgres
libz.so => /usr/lib/libz.so (0x2833f000)
libncurses.so.5 => /shlib/libncurses.so.5 (0x2834e000)
libdl.so => /shlib/libdl.so (0x2838c000)
libm.so => /s
Andrew Dunstan wrote:
Thomas Hallgren wrote:
Problem:
PL/Java use a JVM. On some platforms and with some JVM's (Sun's in
particular) a libzip.so is bundled that contains a 1.1.3 version of
functions also provided in zlib (why they do this is beyond me, but
they do so I'll have to live with it).
Thomas Hallgren wrote:
Problem:
PL/Java use a JVM. On some platforms and with some JVM's (Sun's in
particular) a libzip.so is bundled that contains a 1.1.3 version of
functions also provided in zlib (why they do this is beyond me, but
they do so I'll have to live with it). PostgreSQL is linked
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I'm not sure I understand why keeping track of what we need for each
> executable is such a difficult task, though. I count 23 executables and
> a handful of libraries. Is this such a herculean task?
"Handful"? I count 32 AC_CHECK_LIB and AC_SEARCH_
Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
Am Donnerstag, 23. September 2004 13:02 schrieb Thomas Hallgren:
From what I can understand from the documentation, the only utility in
PostgreSQL that actually uses zlib is pg_dump? If so, why is the
postgres process linked with
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Am Donnerstag, 23. September 2004 13:02 schrieb Thomas Hallgren:
>> From what I can understand from the documentation, the only utility in
>> PostgreSQL that actually uses zlib is pg_dump? If so, why is the
>> postgres process linked with -lz?
> Becau
Peter Eisentraut wrote:
Am Donnerstag, 23. September 2004 13:02 schrieb Thomas Hallgren:
From what I can understand from the documentation, the only utility in
PostgreSQL that actually uses zlib is pg_dump? If so, why is the
postgres process linked with -lz?
Because we are too lazy to fine
Peter Eisentraut wrote:
Because we are too lazy to fine-tune the build system for cases like
this.
The best solution would be to build zlib with symbol versioning.
I'm not so sure. I think zlib is a commodity on most systems. You don't
want to build it at all. Perhaps if I submit a patch that
Am Donnerstag, 23. September 2004 13:02 schrieb Thomas Hallgren:
> From what I can understand from the documentation, the only utility in
> PostgreSQL that actually uses zlib is pg_dump? If so, why is the
> postgres process linked with -lz?
Because we are too lazy to fine-tune the build system fo
Problem:
PL/Java use a JVM. On some platforms and with some JVM's (Sun's in
particular) a libzip.so is bundled that contains a 1.1.3 version of
functions also provided in zlib (why they do this is beyond me, but they
do so I'll have to live with it). PostgreSQL is linked with zlib by
default. T
14 matches
Mail list logo