Re: narwhal and PGDLLIMPORT - Mailing list pgsql-hackers

From Robert Haas
Subject Re: narwhal and PGDLLIMPORT
Date
Msg-id CA+TgmoZXwpFbiC5nacJaXpkPMp_1zp9g5-p=bAJD54J4=RJEjw@mail.gmail.com
Whole thread Raw
In response to Re: narwhal and PGDLLIMPORT  (Dave Page <dpage@pgadmin.org>)
Responses Re: narwhal and PGDLLIMPORT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Feb 3, 2014 at 5:45 AM, Dave Page <dpage@pgadmin.org> wrote:
> Done: http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=narwhal&dt=2014-02-03%2009%3A26%3A43
>
> It's not happy though :-(

Specifically, it says:

dlltool --export-all  --output-def libpg_buffercachedll.def
pg_buffercache_pages.o
dllwrap -o pg_buffercache.dll --dllname pg_buffercache.dll  --def
libpg_buffercachedll.def pg_buffercache_pages.o -L../../src/port
-L../../src/common -Wl,--allow-multiple-definition -L/mingw/lib
-Wl,--as-needed   -L../../src/backend -lpostgres
Info: resolving _MainLWLockArray by linking to __imp__MainLWLockArray
(auto-import)
fu000001.o(.idata$3+0xc): undefined reference to `libpostgres_a_iname'
fu000002.o(.idata$3+0xc): undefined reference to `libpostgres_a_iname'
nmth000000.o(.idata$4+0x0): undefined reference to `_nm__MainLWLockArray'

I assume I should go stick a DLLIMPORT on MainLWLockArray, unless
somebody has another proposal.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: "Tomas Vondra"
Date:
Subject: Re: GIN improvements part2: fast scan
Next
From: Rajni Baliyan
Date:
Subject: Re: [GENERAL] postgres FDW cost estimation options unrecognized in 9.3-beta1