This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: linking with libstdc++
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: Joe Buck <Joe dot Buck at synopsys dot com>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Sun, 28 Jul 2002 12:15:56 -0700
- Subject: Re: linking with libstdc++
- Organization: Red Hat / San Francisco
- References: <20020724145554.F67488@cantrip.org><200207270052.RAA24634@atrus.synopsys.com>
- Reply-to: bkoz at redhat dot com
> At the risk of starting an off-topic thread, I don't understand why
> you believe this. We have two sets of licenses for libraries, the
> LGPL and the GPL-with-special-exception. In either case, there are
> legal ways to distribute statically linked executables even if there
> is proprietary code. There are conditions to be met, yes. If an LGPL
> library is used, there has to be a way of relinking with a newer
> version of the library, but that could be met by a variety of means
> (for example, by distributing proprietary parts as .o files). But the
> libstdc++ license is even looser:
I'm tied up in other work, so don't intend to get into this. However, it
would be helpful Joe if you could think about a way to modify this
wording so as to be more clear:
http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/license.html
I'd appreciate it.
thanks,
benjamin