Re: <SPAM> x86_64-w64-mingw32-g++ options -static-libgcc -static-libstdc++ seems to broken at gcc 9.3.0

Dear Keith,

Many thanks for your detailed reply.

I guess I will just have to look for other avenues to create the Windows shared library perhaps by building on the target Windows platform if cross-compilation is not an option.

Being just one man and a dog, I do not want to get mired down in having to have to learn a whole different IDE world such as Visual Studio so perhaps there something I can explore with the Linux subsystem that ships with Windows 10?

Thanks again for your comments.

-- Michael Ellis

September 4, 2020 5:16 PM, "Keith Marshall" <[email protected]> wrote:

> On 04/09/2020 14:28, Michael Ellis wrote:
> 
>> What exactly is illegal?
> 
> "mingw" (irrespective of any capitalization) is a US registered
> trademark (reg. no. 86017856); it has been registered by SPI Inc., on
> behalf of MinGW.org, and no other project, or organization, is legally
> entitled to use the term "mingw" within their project or product names,
> without seeking authorization from MinGW.org (which none have).
> 
>> Is it the x86_64-w64-mingw32-g++ cross compiler that I am using on my
>> OS-X computer?
> 
> The product name infringes the trademark.
> 
>> I downloaded this using the "brew install mingw-w64" Is this program
>> illegal?
> 
> Once again, "mingw-w64" infringes the trademark.
> 
>> If so, is there a legal cross compiler allowing me to build on OS-X
>> and deeply on Windows?
> 
> The only binaries, legally published by MinGW.org, are for a 32-bit
> natively hosted Windows-32 GCC compiler suite; it simply isn't practical
> for us to maintain binary releases, to support a plethora of non-Windows
> cross-compiler platforms.
> 
> That said, I do build my own mingw32 cross-compiler, for use on my Linux
> hosts, and my build specs are included in the (modified) source tarball,
> as published in MinGW.org FRS. If the distributors of binaries, built
> for non-Windows host were building from our sources, then that would be
> acceptable, but I don't think any do (and certainly, none have sought
> the necessary authorization), so their use of "mingw", within their
> product names, constitutes a trademark violation.
> 
> --
> Regards,
> Keith.
> 
> Public key available from keys.gnupg.net
> Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
> 
> _______________________________________________
> MinGW-Users mailing list
> [email protected]
> 
> 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.osdn.me/mailman/listinfo/mingw-users
> Also: mailto:[email protected]?subject=unsubscribe


Michael Ellis (Managing Director)
Digital Scientific UK Ltd.
http://www.dsuk.biz
[email protected]
tel: +44(0)1223 911215

The Commercial Centre
6 Green End
Cambridge

_______________________________________________
MinGW-Users mailing list
[email protected]

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.osdn.me/mailman/listinfo/mingw-users
Also: mailto:[email protected]?subject=unsubscribe