B. Maust wrote:
> there were a few warnings building plperl:
>
> gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline
> -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -I.
> -I../../../src/include
> -I/System/Library/Perl/5.8.8/darwin-thread-multi-2level/CORE -c -o
> plperl.c: In function '_PG_initg:
> plperl.c:191: warning: passing argument 4 of 'DefineCustomBoolVariableg
> from incompatible pointer type
> plperl.c: In function 'compile_plperl_functiong:
> plperl.c:1624: warning: passing argument 4 of 'SysCacheGetAttrg from
> incompatible pointer type
> plperl.c:1652: warning: passing argument 4 of 'hash_searchg from
> incompatible pointer type
> plperl.c: In function 'plperl_hash_from_tupleg: plperl.c:1685: warning:
> passing argument 4 of 'nocachegetattrg from incompatible pointer type
> plperl.c:1685: warning: passing argument 4 of 'nocachegetattrg from
> incompatible pointer type
> plperl.c:1685: warning: passing argument 4 of 'heap_getsysattrg from
> incompatible pointer type
> plperl.c:1696: warning: passing argument 3 of 'getTypeOutputInfog from
> incompatible pointer type
> plperl.c: In function 'plperl_return_nextg:
> plperl.c:1926: warning: passing argument 3 of 'heap_form_tupleg from
> incompatible pointer type
> plperl.c: In function 'plperl_spi_prepareg:
> plperl.c:2229: warning: passing argument 4 of 'hash_searchg from
> incompatible pointer type
>
> nothing fatal... and a more worrisome warning when linking libperl:
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.
Perhaps a Perl header is redefining "bool" on your platform?
--
Alvaro Herrera http://www.amazon.com/gp/registry/CTMLCN8V17R4
"I love the Postgres community. It's all about doing things _properly_. :-)"
(David Garamond)
