This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH 0/1] Build GDB as a C++ program by default
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Simon Marchi <simon dot marchi at ericsson dot com>
- Cc: palves at redhat dot com, gdb-patches at sourceware dot org
- Date: Tue, 19 Apr 2016 19:02:05 +0300
- Subject: Re: [PATCH 0/1] Build GDB as a C++ program by default
- Authentication-results: sourceware.org; auth=none
- References: <1461000466-31668-1-git-send-email-palves at redhat dot com> <571633C8 dot 4060803 at ericsson dot com> <57163E3B dot 50101 at redhat dot com> <83d1pl8xje dot fsf at gnu dot org> <571651B1 dot 5030607 at ericsson dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> CC: <email@example.com>
> From: Simon Marchi <firstname.lastname@example.org>
> Date: Tue, 19 Apr 2016 11:41:37 -0400
> I wonder why you say that those who distribute a precompiled gdb would
> also have to distribute the gcc source. Do you mean they would have to
> host it alongside the precompiled binary, or they would have to include
> it in the package users download?
The former, of course.
> Isn't it enough that it's available at gcc.gnu.org and/or mingw.org?
No, not according to the GPL. You must make sure the users will be
able to access the exact sources used to build the libraries, and
there's no practical way to ensure that when you point at a site whose
contents you don't control. E.g., nothing prevents mingw.org to
remove the version of GCC I used to build GDB from their site, and
then my link points to the great void.