Skip site navigation (1) Skip section navigation (2)

Help! DLL make faild under windows mingw.

From: Wang Haiyong <wanghaiyong(at)neusoft(dot)com>
To: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Help! DLL make faild under windows mingw.
Date: 2007-05-29 06:50:57
Message-ID: 00a001c7a1bd$b6199810$bc1da8c0@wanghy (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
I am doing a DLL project, it is in the backend/utils/mb. But it can not be maked under windows mingw.
I require everyone to help me. Thank your very much.

The error infomations are as follows.

Info: resolving _CurrentMemoryContext by linking to __imp__CurrentMemoryContext (auto-import)
Info: resolving _SPI_processed by linking to __imp__SPI_processed (auto-import)
Info: resolving _SPI_tuptable by linking to __imp__SPI_tuptable (auto-import)
Info: resolving _default_statistics_target by linking to __imp__default_statistics_target (auto-import)
fu000001.o(.idata$3+0xc): undefined reference to `libpostgres_a_iname'
fu000002.o(.idata$3+0xc): undefined reference to `libpostgres_a_iname'
fu000003.o(.idata$3+0xc): undefined reference to `libpostgres_a_iname'
fu000004.o(.idata$3+0xc): undefined reference to `libpostgres_a_iname'
fu000005.o(.idata$3+0xc): undefined reference to `libpostgres_a_iname'
fu000006.o(.idata$3+0xc): more undefined references to `libpostgres_a_iname' follow
nmth000000.o(.idata$4+0x0): undefined reference to `_nm__CurrentMemoryContext'
nmth000111.o(.idata$4+0x0): undefined reference to `_nm__SPI_processed'
nmth000118.o(.idata$4+0x0): undefined reference to `_nm__SPI_tuptable'
nmth000127.o(.idata$4+0x0): undefined reference to `_nm__default_statistics_target'
d:\MinGW\bin\dllwrap.exe: d:\MinGW\bin\gcc exited with status 1
make: *** [libnsqlgeom.dll] Error 1

Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Group Ltd., its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful. If you have received this communication in error, please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. 


pgsql-hackers by date

Next:From: Hannu KrosingDate: 2007-05-29 08:15:45
Subject: Re: status of PlPython
Previous:From: Jon ColversonDate: 2007-05-29 04:10:45
Subject: Attempt to re-archive existing WAL logs after restoring from backup

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group