From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Thomas Hallgren <thhal(at)mailblocks(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Use of zlib |
Date: | 2004-09-23 16:05:54 |
Message-ID: | 26809.1095955554@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> 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_LIBS calls in
configure.in.
But that's only part of the problem. Consider that many of these
libraries are interdependent to some extent. The raw results from
Autoconf tell you that libfoo is available and we could link with it,
but not whether libfoo requires the previously-checked libbar to link.
We'd need to redo the whole library detection process for each
executable in order to be perfectly accurate about this. Since the
Autoconf macros only cope with one LIBS list, that means throwing away
the Autoconf macros and writing our own.
Multiply that by N supported platforms, and you start to see why this is
a mess. It's certainly work far out of proportion to the actual value
of not linking some unneeded libraries.
Adding "--as-needed" on platforms that support it seems like a
reasonable amount of work to expend in comparison to the value received.
Trying to do it manually does not.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-09-23 16:14:39 | Re: BUG: possible busy loop when connection is closed while trying to establish SSL connection |
Previous Message | Fabien COELHO | 2004-09-23 16:03:16 | Re: BUG: possible busy loop when connection is closed |