Changing top level files and include/ files over to GPLv3

Alexandre Oliva aoliva@redhat.com
Mon Jul 9 14:00:00 GMT 2007


On Jul  6, 2007, DJ Delorie <dj@redhat.com> wrote:

>> Changing libiberty, which is shared between projects, would have the 
>> effect of changing all projects using it (bearing in mind that parts of 
>> libiberty are under the GPL and parts under the LGPL, and both should 
>> probably be updated at once).

> Yeah, libiberty will have to be one of the last ones migrated.
> Fortunately, all its files include the "or later" clause, so an
> unmigrated libiberty can be used with a migrated gcc/gdb/etc.

Actually, since everything else has an "or later" clause, migrating
libiberty would amount to migrating everything else ;-)

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}



More information about the Gcc-patches mailing list