Re: Questions on proprietary program using gcc libraries

[David Kastrup]

"jim.brown" <jim.brown@mindspring.com> writes:

> I've searched this forum and did not find any guidance.
> 
> I am building a proprietary shared library with gcc. The normal
> C++ runtime routines (memcpy etc.) are dynamically linked.

I am assuming that all libraries in question are under the LGPL.

> 1. Can I sell my application since it uses the C runtime.

You can sell applications including GPLed or LGPLed code all you want
to.  The GPL does not restrict the price you can demand, but your
customers may copy and sell appropriately licensed pieces themselves,
if they want to.

> 2. If I sell it, am I correct that it falls under the LGPL license.

No.  The point of the LGPL is that linking in a manner that allows the
customer to independently upgrade the library (such as by dynamic
linking) does not make any demands on how the complete result needs to
get licensed.

> 3. If the person who buys does not have gcc,

That's not your fault, but you should point out where to get it.

>     can I distribute the C++ runtime libraries libgcc_s.so.1
>     libstdc++.so.5 with my product.

If accompanied with the source of the library according to the LGPL,
yes.

>     If so, how do I reference their license?

It will be part of the source package.

> Thanks for the help. I have been unable to interpret the LGPL by myself.

Have you actually read it?  Where is it unclear?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum