Re: static libgcc license?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Adam,

My understanding is that libgcc.a is LGPL, and thus does not GPL "infect" (obligate) your code.

The parts that are NOT LGPL in GCC, and are GPL (and thus obligate your code likewise) are...

These libraries:
+ iberty library.  (e..g, libiberty.a; GNU utility common routines, like the ARM project for Amiga)
+ bfd library.  (e.g., libbfd.a; compiler, debugger support)
+ opcodes library.  (e.g., libopcodes.a; compiler, debugger, disassembler support)

These header files:
+ ansidecl.h (K&R to C89 transition helper)
+ bfd.h (associated with libbfd.a)
+ bfdlink.h (associated with libbfd.a)
+ symcat.h (macro magic for identifier concatenation)
+ dis-asm.h (associated with libopcodes.a)

DISCLAIMER: I'm not a lawyer.  Take my assessment at your own risk.

--Eljay



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux