Re: libgmp-10.dll not found

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>

--
Earnie
-- https://sites.google.com/site/earnieboyd

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
MinGW-users mailing list
MinGW-users@...

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:mingw-users-request@...?subject=unsubscribe