Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


Custom Compiler and Libc Licensing

Posted on 2003-02-26
Medium Priority
Last Modified: 2012-05-04
I am currently working on a compiler/linker for Linux and I have a question related to the licensing of Linux's libc. If I release a compiler that uses libc, and someone compiles a product with it, is their product also subject to the libc licensing (since part of the compiled code may include compiled code from libc as well)?

Basically, I want people to be able to use my compiler to produce their products without worrying about the restrictions of the GNU Library General Public License. Is this possible?
Question by:masterful
  • 2
  • 2

Expert Comment

ID: 8031254
You need to be more specific about how the compiler "uses" libc.  Does the compiler invoke libc routines in the process of generating object code?  Does it take code from libc and put it in its output (which means it is a linker as well as a compiler)?  Does it include libc .h files in the source stream it compiles?

Author Comment

ID: 8033241
Yes, the object files that the linker generates invoke malloc() and friends. I know a dynamicically linked malloc() in their final product would be fine, but if they chose to statically link their application, then would they be forced into the terms of the license?

Accepted Solution

bryanh earned 200 total points
ID: 8034723
They'd be safe.  That's the purpose of the LGPL vs the GPL.

If you combine LGPL code with other code (such as by static linking), and the other code interfaces to the LGPL code only through interfaces intentionally exposed by the LGPL code, you can distribute the combination without having to distribute source code for the other code.

By contrast, if that LGPL code were GPL instead, you would in that case have to distribute the whole combination under the GPL, which includes distributing source for the other code.  At least that's what the inventors of GPL believe.

And note that if the other code linked dynamically to the library, then neither GPL nor LGPL on the library would trigger any restrictions on distributing the other code.  Except that some people believe if the other code implements the interface by #including header files from a GPL library, then the other code must be distributed under GPL.

Author Comment

ID: 8034801
Thank you! I just needed that clarified before I advanced my project any farther. Software licensing can be a major pain to deal with sometimes.

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The purpose of this article is to fix the unknown display problem in Linux Mint operating system. After installing the OS if you see Display monitor is not recognized then we can install "MESA" utilities to fix this problem or we can install additio…
The purpose of this article is to demonstrate how we can upgrade Python from version 2.7.6 to Python 2.7.10 on the Linux Mint operating system. I am using an Oracle Virtual Box where I have installed Linux Mint operating system version 17.2. Once yo…
Loops Section Overview
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses
Course of the Month11 days, 8 hours left to enroll

564 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question