MinGW的＆QUOT;程序输入点libiconv的找不到...＆QUOT; [英] MinGW "The procedure entry point libiconv could not be located ..."

问题描述

我有一个标准C库，使用gcc编译Mac OS X上就好了。

I've got a standard C library that compiles just fine on Mac OS X using gcc.

我已经研究可用于Windows的C编译器，并选择MinGW的一对夫妇的原因：

I've examined the C compilers available for Windows, and choose MinGW for a couple reasons:

• MS的工具不支持C99


• 的Cygwin等。人。增加了与POSIX模拟复杂，我不想额外级别


• 无法获取LCC-win32的工作

但是，当我尝试建立我的图书馆，我得到这样的：

But, when I try to build my library, I'm getting this:

这所有的东西看起来很陈旧，有几乎没有什么像样的在线资源，我可以找到。

This stuff all seems very archaic, and there are practically no decent resources online that I can find.

任何帮助将大大AP preciated。

Any help would be greatly appreciated.

感谢。

编辑：

不要紧，我尝试建立。即使我只是做与两数相加的功能的单个文件。它崩溃。似乎没有有什么与源$ C ​​$ C或传递给GCC在所有选项。我觉得这是我的MinGW的设置，而不是与我的项目有问题。

It doesn't matter what I'm trying to build. Even if I just make a single file with a function that adds two numbers. It crashes. Doesn't seem to have anything to do with the source code or the options passed to gcc at all. I think this is a problem with my MinGW setup and not with my project.

推荐答案

请确保您有C：\\包含任何其他目录之前的MinGW \\ BIN在路径 libiconv的-2.DLL 。显然， as.exe 在一些MinGW的分布是依赖于DLL，某处路径中拥有一个旧版本的它（例如的GnuWin32工具），将导致 as.exe 拿起一个没有切入点它寻找的旧版本。

Make sure you have C:\MinGW\bin in your path before any other directory that contains libiconv-2.dll. Apparently the as.exe in some MinGW distributions are dependent on that DLL, and having an older version of it in the path somewhere (for example GnuWin32 tools) will cause as.exe to pick up the older version that doesn't have the entry point it's looking for.

请参阅：<一href=\"http://sourceforge.net/tracker/index.php?func=detail&aid=3375870&group_id=200665&atid=974439\">http://sourceforge.net/tracker/index.php?func=detail&aid=3375870&group_id=200665&atid=974439

请注意 - 你应该能够取代旧的 libiconv的-2.DLL 与的较新\\ MinGW的\\ BIN - 该DLL的应的意思，它是落后与老一（即旧的不依赖ONT他新的出口应该会继续工作软件）兼容。但是，我还没有测试过，所以一定要备份，如果你决定尝试从你的MinGW安装一个取代冲突的DLL。

Note - you should be able to replace the older libiconv-2.dll with the newer one in \MinGW\bin - the naming of the DLL should mean that it's backward compatible with the older one (ie., older software that isn't dependent ont he newer exports should continue to work). However, I haven't tested that so be sure to backup if you do decide to try replacing the conflicting DLL with the one from your MinGW installation.

这篇关于MinGW的＆QUOT;程序输入点libiconv的找不到...＆QUOT;的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！