| From: | "William ZHANG" <uniware(at)zedware(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Shared library conflicts |
| Date: | 2006-06-23 10:10:11 |
| Message-ID: | e7gem3$1678$1@news.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Thomas Hallgren" <thomas(at)tada(dot)se>
>
> Another related question. What happens when I use --without-zlib? Does it
> have any effect on besides disabling compression for the dump/restore
> utilities? Is there anyway to make it affect the backend only?
--without-zlib will affected LIBS and HAVE_LIBZ defined in configure.
I searched HAVE_LIBZ in the source code, and find only pg_dump use it.
I think we can change LIBS to not include "-lz" in configure, and add "-lz"
for pg_dump in its Makefile.
With regards,
William ZHANG
>
> Kind Regards,
> Thomas Hallgren
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-06-23 10:36:26 | Re: Shared library conflicts |
| Previous Message | Luke Lonergan | 2006-06-23 09:39:38 | Re: vacuum, performance, and MVCC |