On Thu, Jul 27, 2017 at 10:21 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Ashutosh Sharma <ashu.coe...@gmail.com> writes: >> Anyways, attached is the patch that corrects this issue. The patch now >> imports all the switches used by perl into plperl module but, after >> doing so, i am seeing some compilation errors on Windows. Following is >> the error observed, > >> SPI.obj : error LNK2019: unresolved external symbol PerlProc_setjmp >> referenced in function do_plperl_return_next > > That's certainly a mess, but how come that wasn't happening before?
How about we fix it like this? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Description: Binary data
-- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers