This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++ license
- To: drepper at cygnus dot com
- Subject: Re: libstdc++ license
- From: Joe Buck <jbuck at synopsys dot com>
- Date: Fri, 17 Jul 98 21:49:14 PDT
- Cc: egcs at cygnus dot com
> > If a pure C++ program is built with libstdc++ will it contain LGPL parts
> > from the C library (sucked in behind the scenes) assuming I don't
> > explicitly use C library features like malloc, printf, strcpy etc. ?
> > Or is it essentially impossible to legally do what I'd like to do ?
[ like to do == make a proprietary statically linked binary that has LGPL
code in it ]
> You cannot produce a binary using a statically linked libc without
> having your program available under something different then the
> L(GPL).
Last time I parsed the language, it seemed to me that a statically linked
binary is OK if a dynamically linked binary of the same program is also
provided. Am I wrong? That satisfies the requirement that the user
can relink with a new version of the library.
(gnu.misc.discuss is better for this than the egcs list, in theory: on the
other hand you do get harrassed more by anti-[L]GPL crowd).