Message-ID: <4A26FF38.8090308@dunslane.net>
Date: Wed, 03 Jun 2009 18:54:48 -0400
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text
	SeaMonkey/1.0.9
MIME-Version: 1.0
To: Josh Berkus <josh@agliodbs.com>
CC: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Subject: Re: It's June 1; do you know where your release is?
References: <19107.1243873940@sss.pgh.pa.us>
	<603c8f070906012050p6ccd62d3v13d3e0f887fe7c90@mail.gmail.com>
	<alpine.BSO.2.00.0906020108410.15690@leary.csoft.net>
	<15765.1243965376@sss.pgh.pa.us> <4A25C32F.30203@agliodbs.com>
	<4A25C9A9.5010303@dunslane.net> <4A25D91B.5080401@dunslane.net>
In-Reply-To: <4A25D91B.5080401@dunslane.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


Andrew Dunstan wrote:
>
>
> Andrew Dunstan wrote:
>>
>>
>> Josh Berkus wrote:
>>>
>>>
>>>     *  plperl fails with Perl 5.10 on Windows
>>>           o tgl says: no reports of this with pre-8.4 Postgres, but 
>>> I bet that's just because no one tried it
>>>           o dpage says: I'm rolling back the Windows installers to 
>>> use 5.8 for now. Would appreciate help from anyone familiar with 
>>> Perl internals to try to debug this further!
>>>
>>> -- Dunstan, Wheeler, Sabino-Mullaine, 'lil help please?
>>>
>>>
>>
>> I'm working on it.
>
> Well, the first problem we encounter is this gem in the GNUMakefile 
> (and there is an equivalent in the MSVC build setup):
>
>    ifeq ($(*PORTNAME*), win32)
>    perl_archlibexp := $(*subst \,/,$(perl_archlibexp)*)
>    perl_privlibexp := $(*subst \,/,$(perl_privlibexp)*)
>    perl_embed_ldflags = -L$(*perl_archlibexp*)/CORE -lperl58
>    override CPPFLAGS += -DPLPERL_HAVE_UID_GID
>    /# Perl on win32 contains /* within comment all over the header file,
>    //# so disable this warning.
>    /override CFLAGS += -Wno-comment
>    endif
>
> Note the hardcoded perl58 library name.
>
> If we fix that then we get the previously reported crash. I'll try to 
> put some traces in to see exactly why that might be happening.
>
>

Update: the problem is apparently occurring during the call to 
perl_parse() in plperl_init_interp().

Not sure why yet, but that might help other people to concentrate on 
where the problem is.

cheers

andrew