Re: [HACKERS] perl interface bug?

From: Brook Milligan <brook(at)trillium(dot)NMSU(dot)Edu>
To: E(dot)Mergl(at)bawue(dot)de
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] perl interface bug?
Date: 1998-10-15 14:21:13
Message-ID: 199810151421.IAA13089@trillium.nmsu.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas G. Lockhart 1998-10-15 14:28:36 Re: [HACKERS] Re: order by and index path
Previous Message Thomas G. Lockhart 1998-10-15 14:19:31 Re: [HACKERS] PostgreSQL v6.4 BETA2 ...