Thread: postgres.h location?
I'm looking for the file postgres.h in my recent install of postgres-7.4.5 on a MacOS 10.3.5 system. I'm attempting to build PyGreSQL-3.5, which appears to require the postgres include dir. My build of postgres-7.4.5 did produce an include dir, /usr/local/pgsql/include; but it does not contain postgres.h. Curiously, it does contain a file called postgres_ext.h. I'm sure they're not one-and-the-same ... Suggestions? Thanks in advance! Scott
Scott Frankel <leknarf@pacbell.net> writes:
> My build of postgres-7.4.5 did produce an include dir,
> /usr/local/pgsql/include;
> but it does not contain postgres.h.
You need to do "make install-all-headers" while installing to install
the server-side headers there.
regards, tom lane
On Wed, Oct 06, 2004 at 03:27:39PM -0400, Tom Lane wrote: > Scott Frankel <leknarf@pacbell.net> writes: > > My build of postgres-7.4.5 did produce an include dir, > > /usr/local/pgsql/include; > > but it does not contain postgres.h. > > You need to do "make install-all-headers" while installing to install > the server-side headers there. BTW, did this just change in 8.0? The latest CVS sources no longer have an install-all-headers target (GNUmakefile.in 1.41); it looks like the install target installs all headers now. -- Michael Fuhr http://www.fuhr.org/~mfuhr/
Michael Fuhr <mike@fuhr.org> writes:
> On Wed, Oct 06, 2004 at 03:27:39PM -0400, Tom Lane wrote:
>> You need to do "make install-all-headers" while installing to install
>> the server-side headers there.
> BTW, did this just change in 8.0?
There was a proposal to change it, but I dunno if it was committed.
regards, tom lane
The option install-all-headers was removed in the past few days because install by default now installs all headers. --------------------------------------------------------------------------- Tom Lane wrote: > Michael Fuhr <mike@fuhr.org> writes: > > On Wed, Oct 06, 2004 at 03:27:39PM -0400, Tom Lane wrote: > >> You need to do "make install-all-headers" while installing to install > >> the server-side headers there. > > > BTW, did this just change in 8.0? > > There was a proposal to change it, but I dunno if it was committed. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
Default now installs all headers ... with v8.0 of postgres, right? New to postgres (and db's for that matter) I just downloaded the tarball for postgres-7.4.5. Invoking the make install-all-headers cmd did indeed produce the servers subdir under include. Unfortunately, my attempts to build PyGreSQL still return a crudjillion error msgs. But that's a matter for another list ;) Thanks for the feedback - Scott On Oct 6, 2004, at 3:26 PM, Bruce Momjian wrote: > > The option install-all-headers was removed in the past few days because > install by default now installs all headers. > > ----------------------------------------------------------------------- > ---- > > Tom Lane wrote: >> Michael Fuhr <mike@fuhr.org> writes: >>> On Wed, Oct 06, 2004 at 03:27:39PM -0400, Tom Lane wrote: >>>> You need to do "make install-all-headers" while installing to >>>> install >>>> the server-side headers there. >> >>> BTW, did this just change in 8.0? >> >> There was a proposal to change it, but I dunno if it was committed. >> >> regards, tom lane >> >> ---------------------------(end of >> broadcast)--------------------------- >> TIP 6: Have you searched our list archives? >> >> http://archives.postgresql.org >> > > -- > Bruce Momjian | http://candle.pha.pa.us > pgman@candle.pha.pa.us | (610) 359-1001 > + If your life is a hard drive, | 13 Roberts Road > + Christ can be your backup. | Newtown Square, Pennsylvania > 19073 > > ---------------------------(end of > broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html >