From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Thomas Hallgren <thhal(at)mailblocks(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Use of zlib |
Date: | 2004-09-23 14:48:54 |
Message-ID: | 26037.1095950934@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> 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?
> Because we are too lazy to fine-tune the build system for cases like this.
I was just reading about a linker option (--as-needed or something like
that) that exists in more recent versions of the GNU linker. It means
"only link the libraries actually referenced". Applying this or local
equivalent where available would seem like a fairly painless way to
solve the problem, at least on some platforms.
I agree that trying to keep track of the set of libraries really needed
for each executable would be a hopeless task, but if we can make the
linker fix it for us ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-09-23 14:54:01 | Re: SQL-Invoked Procedures for 8.1 |
Previous Message | Tom Lane | 2004-09-23 14:35:23 | Re: NOFIXADE / NOPRINTADE |