| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
| Cc: | "Dann Corbit" <DCorbit(at)connx(dot)com>, "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, "mlw" <pgsql(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: contrib and licensing |
| Date: | 2003-04-03 14:29:39 |
| Message-ID: | 28126.1049380179@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
>>> And its stubs are in the backend, of all places.
>> Really? I must have missed that.
> On Linux as compiled in Red Hat 9, at least:
> [lowen(at)localhost lowen]$ ldd /usr/bin/postgres
> libreadline.so.4 => /usr/lib/libreadline.so.4 (0x401c6000)
That's because our build mechanism links *all* needed libraries in *all*
executables, rather than trying to distinguish which ones are actually
used by each executable. The ldd indication is the only connection to
libreadline --- if it had been a statically-linked situation, you'd find
no trace of readline (nor several other of these libraries, I suspect)
in the backend executable.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Liu | 2003-04-03 14:50:50 | can't create database |
| Previous Message | Jan Wieck | 2003-04-03 14:25:10 | Re: contrib and licensing |