> 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
> 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.
> 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
> > 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
> 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
> 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
Snapshot gcc-13-20250717 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250717/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
> 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.
