Re: Question about GCC license for commercial use

> AFAIU, having the shared libraries in separate files means they are > not "combined" with the program's code. That's how I understand what > RMS told me back then, in the quote that I brought up. Nothing in the GCC Runtime Exception says that the "Target Code" consists of a single file.

Re: Question about GCC license for commercial use

> Date: Thu, 17 Jul 2025 05:23:50 -0700 (PDT) > Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com > From: ken...@adacore.com (Richard Kenner) > > > I don't see how distributing in the same tarball would solve the > > problem. > > > > Suppose I'd decide to distribute a Windows bui

Re: Question about GCC license for commercial use

> I don't see how distributing in the same tarball would solve the > problem. > > Suppose I'd decide to distribute a Windows build of Emacs together > with GNU Grep (e.g., because MS-Windows systems don't come with Grep > OOTB, whereas Emacs users need Grep for several of its features). I > would

Re: Question about GCC license for commercial use

> Date: Thu, 17 Jul 2025 03:43:29 -0700 (PDT) > Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com > From: ken...@adacore.com (Richard Kenner) > > > > Yes, but the discussion wasn't about "as a separate file", but as a file > > > that's part of the distribution of another program.

Re: Question about GCC license for commercial use

> > Yes, but the discussion wasn't about "as a separate file", but as a file > > that's part of the distribution of another program. > > A shared library is always a separate file. Yes, of course. What I meant is that it's not *being distributed separately*. For example, it can be in the same t

Re: Question about GCC license for commercial use

> Date: Thu, 17 Jul 2025 02:28:36 -0700 (PDT) > Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com > From: ken...@adacore.com (Richard Kenner) > > > That's not what RMS told me when I asked him some time ago. He said > > that, since libgcc DLL and libstdc++ DLL are basically separ

Re: Question about GCC license for commercial use

> That's not what RMS told me when I asked him some time ago. He said > that, since libgcc DLL and libstdc++ DLL are basically separate files > and thus separate builds of the libraries, the run-time exception you > pointed to is not applicable to them. Quoting his response back then: > > Ther

Re: Question about GCC license for commercial use

> Date: Wed, 16 Jul 2025 19:03:21 +0200 > Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org > From: David Brown > > >> Well they didn't ask about distributing the DLLs :-) > > > > They did, indirectly: programs compiled by MinGW GCC are linked > > against libgcc and libstdc++ import libraries, and thu

Re: Question about GCC license for commercial use

On 16/07/2025 17:37, Eli Zaretskii via Gcc wrote: From: Jonathan Wakely Date: Wed, 16 Jul 2025 16:12:01 +0100 Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org On Wed, 16 Jul 2025 at 15:59, Eli Zaretskii wrote: Please stop giving bad advice and direct people to read the appropriate documentation.

Re: Question about GCC license for commercial use

> Date: Wed, 16 Jul 2025 17:44:41 +0200 > From: Dennis Luehring via Gcc > > Am 16.07.2025 um 17:37 schrieb Eli Zaretskii via Gcc: > > Unless the Windows loader can find them on > > the end-user's machine, it will refuse to run the program. > > the initial question was: do they fall under GPL whe

Re: Question about GCC license for commercial use

Am 16.07.2025 um 17:37 schrieb Eli Zaretskii via Gcc: Unless the Windows loader can find them on the end-user's machine, it will refuse to run the program. the initial question was: do they fall under GPL when just using gcc - how complex or error prone their distribution concepts get is of no

Re: Question about GCC license for commercial use

> From: Jonathan Wakely > Date: Wed, 16 Jul 2025 16:12:01 +0100 > Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org > > On Wed, 16 Jul 2025 at 15:59, Eli Zaretskii wrote: > > > > > Please stop giving bad advice and direct people to read the > > > appropriate documentation. > > > > Why the animosity?

Re: Question about GCC license for commercial use

On Wed, 16 Jul 2025 at 15:59, Eli Zaretskii wrote: > > > From: Jonathan Wakely > > Date: Wed, 16 Jul 2025 15:08:50 +0100 > > Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org > > > > > > AFAIU, this is accurate if libgcc and libstdc++ are linked statically, > > > > but not if the program is linked to t

Re: Question about GCC license for commercial use

> From: Jonathan Wakely > Date: Wed, 16 Jul 2025 15:08:50 +0100 > Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org > > > > AFAIU, this is accurate if libgcc and libstdc++ are linked statically, > > > but not if the program is linked to their DLL versions (and therefore > > > the DLLs must be distribut

Re: Question about GCC license for commercial use

On Wed, 16 Jul 2025 at 15:06, Jonathan Wakely wrote: > > On Wed, 16 Jul 2025 at 13:21, Eli Zaretskii wrote: > > > > > Date: Wed, 16 Jul 2025 11:12:44 +0100 > > > Cc: gcc , gcc-help > > > From: Jonathan Wakely via Gcc > > > > > > On Wed, 16 Jul 2025 at 10:06, Qifan.Zhou via Gcc wrote: > > > > >

Re: Question about GCC license for commercial use

On Wed, 16 Jul 2025 at 13:21, Eli Zaretskii wrote: > > > Date: Wed, 16 Jul 2025 11:12:44 +0100 > > Cc: gcc , gcc-help > > From: Jonathan Wakely via Gcc > > > > On Wed, 16 Jul 2025 at 10:06, Qifan.Zhou via Gcc wrote: > > > > > > Dear GCC Team, > > > > Please don't email both gcc@gcc.gnu.org and

Re: Question about GCC license for commercial use

> Date: Wed, 16 Jul 2025 06:49:23 -0700 (PDT) > Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com > From: ken...@adacore.com (Richard Kenner) > > > Not if we are talking about Windows binaries intended to be used by > > people who don't have GCC installed. (The OP asked about Min

Re: Question about GCC license for commercial use

> Not if we are talking about Windows binaries intended to be used by > people who don't have GCC installed. (The OP asked about MinGW, which > is why I bring up this case.) These DLLs are part of the MinGW GCC > installation, but do not come with the OS OOTB. But then what the OP could do is to

Re: Question about GCC license for commercial use

> Date: Wed, 16 Jul 2025 06:20:42 -0700 (PDT) > Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com > From: ken...@adacore.com (Richard Kenner) > > > AFAIU, this is accurate if libgcc and libstdc++ are linked statically, > > but not if the program is linked to their DLL versions (an

Re: Question about GCC license for commercial use

> AFAIU, this is accurate if libgcc and libstdc++ are linked statically, > but not if the program is linked to their DLL versions (and therefore > the DLLs must be distributed with the resulting program). In the > latter case, the LGPL exception doesn't apply, and distributing these > DLLs falls u

Re: Question about GCC license for commercial use

> Date: Wed, 16 Jul 2025 11:12:44 +0100 > Cc: gcc , gcc-help > From: Jonathan Wakely via Gcc > > On Wed, 16 Jul 2025 at 10:06, Qifan.Zhou via Gcc wrote: > > > > Dear GCC Team, > > Please don't email both gcc@gcc.gnu.org and gcc-h...@gcc.gnu.org, pick > the appropriate one. You're not discussin

Re: Question about GCC license for commercial use

On Wed, 16 Jul 2025 at 10:06, Qifan.Zhou via Gcc wrote: > > Dear GCC Team, Please don't email both gcc@gcc.gnu.org and gcc-h...@gcc.gnu.org, pick the appropriate one. You're not discussing development of GCC so this belongs on the gcc-help list. Anyway ... > I hope this message finds you well.

Question about GCC license for commercial use

Dear GCC Team, I hope this message finds you well. I'm writing to seek official clarification regarding the use of GCC compilers in our proprietary, closed-source commercial software development. Our specific use case involves: 1. Using GCC executables (gcc.exe, g++.exe, etc.