Re: [HACKERS] perl interface bug? - Mailing list pgsql-hackers

From Brook Milligan
Subject Re: [HACKERS] perl interface bug?
Date
Msg-id 199810151421.IAA13089@trillium.nmsu.edu
Whole thread Raw
In response to Re: [HACKERS] perl interface bug?  (Edmund Mergl <E.Mergl@bawue.de>)
Responses Re: [HACKERS] perl interface bug?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
   I think the best solution is just not to build the perl interface
   together with postgresql. It will never work, because 'make test'
   needs the postmaster to be up and running.

I will argue strongly that we DO want to build the perl interface
straight out of the box.  Ideally we will have a COMPLETE system that
can be built and installed in one pass, such that every part of it
will work.  I have demonstrated that it is possible (at least on
NetBSD) to do this and still resolve the inter-library references
between the perl interface and libpq.

We cannot kill this idea because 'make test' doesn't run without the
postmaster.  After all, NONE of the regression tests do either!
Nevertheless, we still build and install the complete system; then run
the tests.  The same is applicable to the perl interface.

   Don't change Makefile.PL, POSTGRES_HOME is needed when building the perl
   module outside the postgresql source-tree.

This may be the case and is a good reason to include the conditional
in Makefile.PL.  Nothing is really lost by doing so.

Cheers,
Brook

pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] PostgreSQL v6.4 BETA2 ...
Next
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Re: order by and index path