Re: [HACKERS] Perl build fix attempted

2002-06-09 Thread Tom Lane
Further digging: the backtrace from the SIGSEGV looks like #0 0xc00a02fc in ?? () from /usr/lib/libc.1 malloc + 1132 #1 0xc267cbb4 in ?? () Perl_sv_grow + 244 from /opt/perl5.6.1/lib/5.6.1/PA-RISC2.0/CORE/libperl.sl #2 0xc26815b0 in ?? () Perl_sv_setpv + 312 from

Re: [HACKERS] Perl build fix attempted

2002-06-09 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Tom Lane writes: >> On HPUX 10.20, using perl 5.6.1, plperl builds without complaint but >> SIGSEGV's upon use. AFAIR this worked last time I tried it; any idea >> what you might have changed? > I have written it so that the commands that are execut

Re: [HACKERS] Perl build fix attempted

2002-06-01 Thread Peter Eisentraut
Tom Lane writes: > On HPUX 10.20, using perl 5.6.1, plperl builds without complaint but > SIGSEGV's upon use. AFAIR this worked last time I tried it; any idea > what you might have changed? I have written it so that the commands that are executed during the build should be the same. Can you se

Re: [HACKERS] Perl build fix attempted

2002-05-30 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > The Perl build (PL/Perl and the Pg interface) now use the configured > compiler and flags and none of the MakeMaker stuff. (I've kept the > interfaces/perl5/Makefile.PL file in case someone wants to resurrect it > for a Win32 build, for instance.) S

[HACKERS] Perl build fix attempted

2002-05-28 Thread Peter Eisentraut
The Perl build (PL/Perl and the Pg interface) now use the configured compiler and flags and none of the MakeMaker stuff. (I've kept the interfaces/perl5/Makefile.PL file in case someone wants to resurrect it for a Win32 build, for instance.) Since doing Perl builds without MakeMaker is poorly do