Re: [BUGS] perl 5.6.0 almost working!

2000-04-05 Thread John M. Flinchbaugh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 5 Apr 2000, Tom Lane wrote: > Has anyone else tried to use plperl? Either success or failure > reports would be useful at this point. i've build the plperl.so without error, but i have not actually tested it to see how it works. i'm unfortu

Re: [BUGS] perl 5.6.0 almost working!

2000-04-05 Thread John M. Flinchbaugh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 5 Apr 2000, Bruce Momjian wrote: > Got it. Done. I was confused between plperl and interfaces/perl. I > assume plperl still does not work, right? that one seems to have been fixed already for beta4, so it works wonderfully. __

Re: [BUGS] perl 5.6.0 almost working!

2000-04-05 Thread John M. Flinchbaugh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 5 Apr 2000, Bruce Momjian wrote: > > it seems in src/interfaces/Makefile, the perl5/Makefile rule gets the > > POLLUTE=1 option as necessary, which makes it work for make all, but > > doing a ``make install'' uses the perl5-install, which does

[BUGS] perl 5.6.0 almost working!

2000-04-05 Thread John M. Flinchbaugh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 it seems in src/interfaces/Makefile, the perl5/Makefile rule gets the POLLUTE=1 option as necessary, which makes it work for make all, but doing a ``make install'' uses the perl5-install, which does not build the perl5/Makefile with POLLUTE=1. _

[BUGS] postgresql 7.0beta2&3 with perl 5.6.0

2000-03-27 Thread John M. Flinchbaugh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 i sent a little note about postgresql 7.0beta2 not working with perl 5.6.0 nicely. beta3 still has the problem. it seems that with perl 5.6.0, the makefiles for pl/plperl and interfaces/perl5 need to be built with: perl Makefile.PL POLLUTE=1 this t

[BUGS] Pg.pm and perl 5.6.0

2000-03-26 Thread John M. Flinchbaugh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 i managed to build Pg.pm by running: perl Makefile.PL POLLUTE=1 that turns on some macros to provide some deprecated global variables upon which Pg.pm seems to still rely. }John Flinchbaugh{__ | [EMAIL PROTECT

[BUGS] Pg.pm and perl 5.6.0

2000-03-25 Thread John M. Flinchbaugh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 the problem looks like it is quite beyond me. here is my error: gcc -c -I../libpq -I../../include -D_REENTRANT -fno-strict-aliasing - -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 - -DVERSION=\"1.8.0\" -DXS_VERSION=\"1.8.0\" -fp

[BUGS] Pg.pm with perl 5.6.0

2000-03-25 Thread John M. Flinchbaugh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pg.pm compiles fine with perl 5.00503, but it fails with perl 5.6.0. i'm under the impression that perl 5.6.0 is the latest stable, so i guess it should be made to work before the release. i don't know much about perl modules, but i'll take a crack

[BUGS] pg_dumpall POSTGRES_USER and ENCODING

2000-03-18 Thread John M. Flinchbaugh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 it seems in the beta2 release DBUSERID in pg_dumpall is the _name_ of the user, so it doesn't need to be translated from the number to the name. also ``create database ...'' does not take numbers for the encoding, so the ENCODING variable does not ne