Re: plperl failure on OS X 10.5(.1) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plperl failure on OS X 10.5(.1)
Date
Msg-id 11826.1195663154@sss.pgh.pa.us
Whole thread Raw
In response to Re: plperl failure on OS X 10.5(.1)  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: plperl failure on OS X 10.5(.1)  (Brandon Maust <bmaust@u.washington.edu>)
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Nothing fatal?  Huh, you have a curious idea about warnings.  This makes
> me think you have the wrong headers or something -- the argument
> mentioned in all these cases is bool, so maybe there is an ABI
> incompatibility somewhere.

Yeah, and it's hardly difficult to see how that might lead to the
reported "null prosrc" error, either.
       bool        isnull;       ...       prosrcdatum = SysCacheGetAttr(PROCOID, procTup,
      Anum_pg_proc_prosrc, &isnull);       if (isnull)           elog(ERROR, "null prosrc");
 

> Perhaps a Perl header is redefining "bool" on your platform?

Seems the question is not so much about OS X as it is about what
perl you're using ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgres 8.3 archive_command
Next
From: Simon Riggs
Date:
Subject: Re: Postgres 8.3 archive_command