Menu
▾
▴
#2257 MinGW can't find its own libraries (cc1.exe fails)
Installed the basic mingw system, attempted to compile a .c file, popped up "libgmp-10.dll not found on your system" error.
Someone reported this on the cmake mailing list with a ... "solution", but you guys can't exactly be expected to monitor the cmake mailing list, so it sort of needs to be actually mentioned here upstream, I think.
Maybe MinGW stopped looking for libraries by its executable path again, and needs to fix/reimplement that. Maybe MinGW needs to add its bin directory to the Path variable. But it certainly doesn't make for a sensible installation, if afterwards you have to look up the path MingW is installed at, go into advanced Microsoft settings and add the path to a variable, before the C compiler will work.
Do you need the entire "developer" installation just to use the C compiler? I haven't tried that, but if so, then there ought to be a note in the basic meta-package, along the lines of "Even though this installs the C compiler, you can't use the C compiler." Or perhaps omitting gcc from basic entirely, leaving you with... uh... bash?
Discussion
Closing as "Invalid -- Behaves as Documented".
Users are expected to update the PATH appropriately, and it is so documented in the installation instructions. Since the user also gets to choose the installation directory himself, when running the installer, it shouldn't be much of a hardship for him to know exactly where the appropriate PATH should point.
I will not have the installer fiddle with PATH settings, (or any other environment variable settings), which should rightfully and strictly be the responsibility of the user to decide -- most sane users will want to set this in a batch file, which initialises the shell for each MinGW session, (as MSYS does, in its initialisation script).