Re: narwhal and PGDLLIMPORT

From: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: narwhal and PGDLLIMPORT
Date: 2014-02-13 00:51:30
Message-ID: 52FC1712.4020307@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(2014/02/12 12:28), Inoue, Hiroshi wrote:
> (2014/02/12 8:30), Tom Lane wrote:
>> I wrote:
>>> Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> writes:
>>>> I tried MINGW port with the attached change and successfully built
>>>> src and contrib and all pararell regression tests were OK.
>>
>>> I cleaned this up a bit (the if-nesting in Makefile.shlib was making
>>> my head hurt, not to mention that it left a bunch of dead code) and
>>> committed it.
>>
>> Hm ... according to buildfarm member narwhal, this doesn't work so well
>> for plperl:
>>
>> gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -g -Wno-comment -shared -o plperl.dll plperl.o SPI.o Util.o -L../../../src/port -L../../../src/common -Wl,--allow-multiple-definition -L/mingw/lib -Wl,--as-needed -LC:/Perl/lib/CORE -lperl58 -L../../../src/backend -lpostgres -lpgcommon -lpgport -lintl -lxslt -lxml2 -lssleay32 -leay32 -lz -lm -lws2_32 -lshfolder -Wl,--export-all-symbols -Wl,--out-implib=libplperl.a
>> Cannot export .idata$4: symbol not found
>> Cannot export .idata$5: symbol not found
>> Cannot export .idata$6: symbol not found
>> Cannot export .text: symbol not found
>> Cannot export perl58_NULL_THUNK_DATA: symbol not found
>> Creating library file: libplperl.a
>> collect2: ld returned 1 exit status
>> make[3]: *** [plperl.dll] Error 1
>
> Oops I forgot to inclule plperl, tcl or python, sorry. I would
> retry build operations with them. Unfortunately it would take
> pretty long time because build operations are pretty (or veeery
> in an old machine) slow.
>
>> Not very clear what's going on there; could this be a problem in
>> narwhal's admittedly-ancient toolchain?

As for build, plperl and pltcl are OK on both Windows7+gcc4.6.1
machine and Windows Vista+gcc3.4.5 machine. plpython is OK on
gcc4.6.1 machine but causes a *initializer element is not constant*
error on gcc3.4.5 machine.
I've not run regression test yet.

regards,
Hiroshi Inoue

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2014-02-13 02:04:45 Re: psql should show disabled internal triggers
Previous Message Craig Ringer 2014-02-13 00:35:32 Re: narwhal and PGDLLIMPORT