Re: tsearch2 windows make failure - Mailing list pgsql-hackers

From Tom Lane
Subject Re: tsearch2 windows make failure
Date
Msg-id 26928.1098120684@sss.pgh.pa.us
Whole thread Raw
In response to tsearch2 windows make failure  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: tsearch2 windows make failure
Re: tsearch2 windows make failure
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> ../../src/Makefile.shlib:327: warning: overriding commands for target `libtsearch2.a'
> ../../src/Makefile.shlib:262: warning: ignoring old commands for target `libtsearch2.a'

Broken coding in the WIN32 parts of Makefile.shlib?  I don't see this
here.

> wparser_def.c:79:1: warning: "IDIGNORE" redefined
> rewrite.c:177:1: warning: "V_UNKNOWN" redefined

Thanks Microsoft :-(  ... guess we'll have to rename those macros.

> Info: resolving _my_exec_path by linking to __imp__my_exec_path (auto-import)
> fu000001.o(.idata$3+0xc): undefined reference to `libpostgres_a_iname'
> nmth000000.o(.idata$4+0x0): undefined reference to `_nm__my_exec_path'

I was wondering whether my_exec_path might need to be marked DLLIMPORT.
Not sure about the other symbol though.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Using ALTER TABLESPACE in pg_dump
Next
From: Tom Lane
Date:
Subject: Re: gettext calls in pgport