MinGW “The procedure entry point libiconv could not be located …”

Question

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

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

Answer 1

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.

See: http://sourceforge.net/tracker/index.php?func=detail&aid=3375870&group_id=200665&atid=974439

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.

Answer 2

In addition to making sure C:\MinGW\bin is in your PATH before anything else, you should also restart your machine (or possibly log out/log in), to ensure your PATH is actually updated.