(2014/02/15 2:32), Tom Lane wrote: > I wrote: >> Hiroshi Inoue <in...@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 ...
There seems some risk to link msvc import library. Linking perlxx.lib or tcl.lib worls here but linking pythonxx.lib doesn't work even in newer machine. > (BTW, narwhal is evidently not trying to build plpython. I wonder > why not?) Due to *initializer element is not constant* error which also can be see on my old machine. http://www.postgresql.org/message-id/CA+OCxozr=0wkQDF7kfd2n-bJQOwdSUs0Myohg29pA_U5=2p...@mail.gmail.com regards, Hiroshi Inoue -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers