Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id LAA60436
	for <pgsql-interfaces@hub.org>; Sat, 2 Oct 1999 11:53:51 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA01795;
	Sat, 2 Oct 1999 11:52:09 -0400 (EDT)
To: Lamar Owen <lamar.owen@wgcr.org>
cc: Brian P Millett <bpm@ec-group.com>, John Cusick <jcusick@exotrope.net>,
	pgsql-interfaces@hub.org
Subject: Re: [INTERFACES] PL_na undeclared 
In-reply-to: Your message of Fri, 01 Oct 1999 13:28:05 -0400
	<37F4EF25.E26D6BD7@wgcr.org>
Date: Sat, 02 Oct 1999 11:52:08 -0400
Message-ID: <1793.938879528@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Lamar Owen <lamar.owen@wgcr.org> writes:
> Uh, Tom, the Pg module works for me under Perl _5.00503_.  The test.pl
> script completes and all that.  The key is building the module with the
> version of perl that the module is going to run against (and rebuilding
> the module when you upgrade perl).

Hmm.  But IIRC, the complaints were from people who were trying and
failing to build the Pg module in the first place.  Could it be that
they have mucked-up Perl installations (headers different revision
from Perl binary, or some such)?

			regards, tom lane