| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | stimits(at)comcast(dot)net |
| Cc: | postgresql <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: more on undefined reference to 'pg_detoast_datum' |
| Date: | 2003-10-13 14:42:40 |
| Message-ID: | 14311.1066056160@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-interfaces |
"D. Stimits" <stimits(at)comcast(dot)net> writes:
> ... My question is, where the heck is
> CurrentMemoryContext and MemoryContextAlloc provided as an
> implementation which I can link with?
They're inside the backend, and you don't --- you are not trying to
build a standalone executable with no unresolved symbols, but a shared
library that can be successfully loaded into the backend. It's okay
for such a library to have unresolved references to symbols that will be
resolved at load time.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Link | 2003-10-13 15:25:17 | Re: A conditional DROP TABLE function |
| Previous Message | Tom Lane | 2003-10-13 14:38:30 | Re: libreadline.so.4 problems on solaris |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2003-10-13 16:06:58 | Re: more on undefined reference to 'pg_detoast_datum' |
| Previous Message | D. Stimits | 2003-10-13 08:39:59 | Re: more on undefined reference to 'pg_detoast_datum' |