This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Proprietary software with modified version of libstdc++..
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Pankaj Chauhan <pchauhan at calypto dot com>
- Cc: "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Date: Thu, 6 Nov 2014 03:24:46 +0000
- Subject: Re: Proprietary software with modified version of libstdc++..
- Authentication-results: sourceware.org; auth=none
- References: <545ADFDF dot 8050702 at calypto dot com>
On 6 November 2014 02:41, Pankaj Chauhan wrote:
> Hi,
>
> I wanted to get your opinion about shipping proprietary software built with
> a version of libstdc++ that we had to modify to address the bug below.
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17215
>
> This has hit us really hard, manifesting in multiple, painful to debug
> crashes.
Why do you need to use such an ancient version then?
> Does the GPL+exceptions license of libstdc++ allow use to ship our software,
> where we have modified the version of fstream? If not, it effectively means
> we have to invent our own fstream, or use plain C style file I/O.
Ask a lawyer and read http://www.gnu.org/licenses/gcc-exception-faq.html
Assuming your modified version is GPL-compatible this is relevant:
"So, if you use GCC, with or without GPL-compatible enhancements, that
would be an Eligible Compilation Process."