Обсуждение: postgres 7.1.3 wth perl 5.8.0
Hi,
i was trying to install postgres 7.1.3 on Redhat 9, using perl 5.8.0-88.3,
./configure --enable-multibyte --enable-odbc --with-perl --with-java
--with-tcl
but make fails on plperl:
gcc -c -I../../../src/include -D_REENTRANT -D_GNU_SOURCE
-DTHREADS_HAVE_PIDS -DDEBUGGING -fno-strict-aliasing
-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/usr/include/gdbm -O2 -march=i386 -mcpu=i686 -g -DVERSION=\"\"
-DXS_VERSION=\"\" -fPIC
"-I/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE" plperl.c
In file included from plperl.c:80:
/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE/perl.h:2537:1:
warning: "DEBUG" redefined
In file included from ../../../src/include/postgres.h:49,
from ../../../src/include/executor/spi.h:15,
from plperl.c:51:
../../../src/include/utils/elog.h:23:1: warning: this is the location of
the previous definition
plperl.c: In function `plperl_init_all':
plperl.c:195: `my_perl' undeclared (first use in this function)
plperl.c:195: (Each undeclared identifier is reported only once
plperl.c:195: for each function it appears in.)
plperl.c: In function `plperl_init_safe_interp':
plperl.c:243: warning: passing arg 2 of `perl_parse' from incompatible
pointer type
plperl.c:251: `my_perl' undeclared (first use in this function)
plperl.c: In function `plperl_create_sub':
plperl.c:320: `my_perl' undeclared (first use in this function)
plperl.c: In function `plperl_init_shared_libs':
plperl.c:387: `my_perl' undeclared (first use in this function)
plperl.c:387: warning: passing arg 3 of `Perl_newXS' from incompatible
pointer type
plperl.c:388: warning: passing arg 3 of `Perl_newXS' from incompatible
pointer type
plperl.c: In function `plperl_call_perl_func':
plperl.c:399: `my_perl' undeclared (first use in this function)
plperl.c: In function `plperl_func_handler':
plperl.c:500: `my_perl' undeclared (first use in this function)
plperl.c: In function `plperl_build_tuple_argument':
plperl.c:2159: `my_perl' undeclared (first use in this function)
make[4]: *** [plperl.o] Error 1
make[4]: Leaving directory `/home/postgres1/postgresql-7.1.3/src/pl/plperl'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/postgres1/postgresql-7.1.3/src/pl/plperl'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/postgres1/postgresql-7.1.3/src/pl'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/postgres1/postgresql-7.1.3/src'
make: *** [all] Error 2
somebody know how to fix this problem?
thanks,
chris
Christian <christian@dnet.net.id> writes:
> i was trying to install postgres 7.1.3 on Redhat 9, using perl 5.8.0-88.3,
> ...
> somebody know how to fix this problem?
Use a later release.
Seriously, 7.1.* is not supported anymore. There are extremely serious
known bugs in it that will never be fixed. I can't imagine a reason for
you to be trying to build it rather than something more current.
regards, tom lane
Tom Lane wrote: > Use a later release. > > Seriously, 7.1.* is not supported anymore. There are extremely serious > known bugs in it that will never be fixed. I can't imagine a reason for > you to be trying to build it rather than something more current. > actually, we are upgrading our system the previously using Redhat 7.1 and Postgres 7.1.3, and upgrading postgres meaning we have to update our applications too, and that's probably out of question. so.. is there a way to fix this without upgrading postgres, but not using Redhat 7.x ? thanks, chris
On Thu, Aug 12, 2004 at 12:05:49PM +0700, Christian wrote: > Tom Lane wrote: > > >Use a later release. > > > >Seriously, 7.1.* is not supported anymore. There are extremely > >serious known bugs in it that will never be fixed. I can't imagine > >a reason for you to be trying to build it rather than something > >more current. > > actually, we are upgrading our system the previously using Redhat > 7.1 and Postgres 7.1.3, and upgrading postgres meaning we have to > update our applications too, and that's probably out of question. Are you going to support your own branch of PostgreSQL in perpetuity? That's what you're signing up for if you don't upgrade. > so.. is there a way to fix this without upgrading postgres, but not > using Redhat 7.x ? No. Cheers, D -- David Fetter david@fetter.org http://fetter.org/ phone: +1 510 893 6100 mobile: +1 415 235 3778 Remember to vote!