On Sun, Mar 20, 2016 at 11:36 AM, Ray Donnelly <[email protected]> wrote: > On Sat, 19 Mar 2016 21:52 Phillip Lord, <[email protected]> wrote: >> >> >> >> I've noticed that the dependencies of libXpm-noX4.dll differs between >> the 64 and 32 bit versions. Specifically, the former doesn't have any, >> while the latter depends on libgcc_s_dw2-1.dll and libwinpthreads.dll. >> >> Is this deliberate? I'd rather not have to distribute libgcc_s_dw2-1, as >> this will require source distribution also. > > > libgcc, as a target GCC library, falls under the runtime exception (provided > you don't emit intermediate compilation representations and process them > with GPL-incompatible code generators on the way to final object files) > > From: http://www.gnu.org/licenses/gcc-exception-3.1-faq.en.html > > "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." >
Sorry, you are right and I should have read more carefully: "I use a proprietary compiler toolchain without any parts of GCC to compile my program, and link it with libstdc++. My program itself does not include any runtime library code the same way that GCC-compiled programs include libgcc. Can I still take advantage of the exception? Yes. While combining libgcc with GCC-compiled object code is probably the most common way the exception is used, neither the GPL nor the GCC Runtime Library Exception distinguish between static linking, dynamic linking, and other methods for combining code in their conditions. The same permissions are available to you, under the same terms, no matter which method you use. Note that if you distribute libstdc++ as an independent library, you will need to follow the terms of the GPL when doing so. For example, if you distribute the library itself in object code form, you will need to provide source code to your recipients using one of the methods listed in section 6 of GPLv3. But as long as you are eligible to take advantage of the GCC Runtime Library Exception's permissions for your own program, the GPL's terms do not extend to it." > But it sounds like something that we should investigate, the former should > also link to libgcc and winpthreads, or neither should. It's *probably* not > serious, but if you want to ensure there's a record of it, please open a bug > regarding the DLL mismatch at > https://github.com/Alexpux/MINGW-packages/issues > > Best regards, > > Ray. > >> >> Phil >> >> >> ------------------------------------------------------------------------------ >> Transform Data into Opportunity. >> Accelerate data analysis in your applications with >> Intel Data Analytics Acceleration Library. >> Click to learn more. >> http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 >> _______________________________________________ >> Msys2-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/msys2-users ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
