Re: libgmp-10.dll not found

>
> > Date: Wed, 11 Apr 2012 08:53:50 -0400
> > From: Earnie Boyd <earnie@...>
> >
> > On Tue, Apr 10, 2012 at 3:51 PM, Eli Zaretskii wrote:
> > > And there are other considerations, apart of versions.  Take, for
> > > example, the decision to distribute libgcc as a DLL -- AFAIU, it
> > > forces anyone who wants to distribute MinGW-compiled packages that
> > > depend on libgcc to also distribute the humongous 80MB GCC source
> > > tarball, by virtue of the GPL.  For example, the latest MinGW build of
> > > bzip2, a very small package in itself, would have to be accompanied by
> > > a 80MB GCC tarball.  Some will find this not to be a problem, but some
> > > will.  There are choices to be made.
> >
> > Uh, no, see COPYING.RUNTIME in the /mingw/share/doc/gcc/GCC-VERSION/
> > directory.
> >
> > <quote>
> > 1. Grant of Additional Permission.
> >
> > You have permission to propagate a work of Target Code formed by
> > combining the Runtime Library with Independent Modules, even if such
> > propagation would otherwise violate the terms of GPLv3, provided that
> > all Target Code was generated by Eligible Compilation Processes. You
> > may then convey such a combination under terms of your choice,
> > consistent with the licensing of the Independent Modules.
> > </quote>
>
> I asked Richard Stallman about this, sending him COPYING.RUNTIME from
> the latest release 4.7.0 of GCC, and here is his response:
>
>  There is nothing in this exception that would permit distribution
>  of libgcc itself -- as a separate file -- other than under the GPL.
>
> As part of discussing this with Richard, he said that libgcc ought to
> allow building it separately, not as part of the whole of GCC, and if
> so, only the small libgcc/ subdirectory of the GCC sources needs to be
> distributed together with the libgcc DLL.  However, trying to build
> libgcc alone fails, at least in GCC 4.7.0, the latest official
> release.
>
> Therefore, my interpretation was correct, and anyone who distributes a
> package that depends on libgcc DLL needs also to distribute the entire
> GCC source tarball.  Since latest MinGW builds of many GNU libraries
> depend on libgcc DLL, any package using those libraries will also
> depend on libgcc DLL, and distributing them requires having the GCC
> tarball nearby.