Re: narwhal and PGDLLIMPORT - Mailing list pgsql-hackers

From Tom Lane
Subject Re: narwhal and PGDLLIMPORT
Date
Msg-id 8923.1392399178@sss.pgh.pa.us
Whole thread Raw
In response to Re: narwhal and PGDLLIMPORT  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: narwhal and PGDLLIMPORT  (Hiroshi Inoue <inoue@tpf.co.jp>)
Re: narwhal and PGDLLIMPORT  (Hiroshi Inoue <inoue@tpf.co.jp>)
Re: narwhal and PGDLLIMPORT  (Dave Page <dpage@pgadmin.org>)
List pgsql-hackers
I wrote:
> Hiroshi Inoue <inoue@tpf.co.jp> writes:
>> One thing I'm wondering about is that plperl is linking perlxx.lib
>> not libperlxx.a. I made a patch following plpython and it also
>> works here.
>> Is it worth trying?

> I hadn't noticed that part of plpython's Makefile before.  Man,
> that's an ugly technique :-(.  Still, there's little about this
> platform that isn't ugly.  Let's try it and see what happens.

And what happens is this:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=narwhal&dt=2014-02-14%2017%3A00%3A02
namely, it gets through plperl now and then chokes with the same
symptoms on pltcl.  So I guess we need the same hack in pltcl.
The fun never stops ...

(BTW, narwhal is evidently not trying to build plpython.  I wonder
why not?)
        regards, tom lane



pgsql-hackers by date:

Previous
From: Jerry Sievers
Date:
Subject: Re: HBA files w/include support?
Next
From: Florian Pflug
Date:
Subject: Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease