Skip site navigation (1) Skip section navigation (2)

Re: more on undefined reference to 'pg_detoast_datum'

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 (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-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

In response to

pgsql-interfaces by date

Next:From: Jan WieckDate: 2003-10-13 16:06:58
Subject: Re: more on undefined reference to 'pg_detoast_datum'
Previous:From: D. StimitsDate: 2003-10-13 08:39:59
Subject: Re: more on undefined reference to 'pg_detoast_datum'

pgsql-general by date

Next:From: David LinkDate: 2003-10-13 15:25:17
Subject: Re: A conditional DROP TABLE function
Previous:From: Tom LaneDate: 2003-10-13 14:38:30
Subject: Re: libreadline.so.4 problems on solaris

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group