Syslinux - Mar 2010 - com32 license restrictions

Hello,

  Would com32 modules be considered the same as an ordinary Linux
executable with respect to LGPL? That is, as long as you released any
changes to syslinux/com32 libs would you also have to release the
source to the com32 module?

Thanks for your time.

On 03/08/2010 02:47 PM, Don Hiatt wrote:
> Hello,
> 
>   Would com32 modules be considered the same as an ordinary Linux
> executable with respect to LGPL? That is, as long as you released any
> changes to syslinux/com32 libs would you also have to release the
> source to the com32 module?
> 
> Thanks for your time.
> 
There is no LGPL code involved.

If you use libcom32.a code only, that code is MIT licensed; you do not
need to share code to either the library or the module.

If you use code out of the gpllib directory -- libcom32gpl.a -- then you
are subject to the GPL and have to release source code to both your
module and to the library (easiest done by distributing a copy of the
Syslinux source code, of course.)

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

On Mon, Mar 8, 2010 at 5:21 PM, H. Peter Anvin <hpa at zytor.com>
wrote:
> There is no LGPL code involved.
>
> If you use libcom32.a code only, that code is MIT licensed; you do not
> need to share code to either the library or the module.
>
> If you use code out of the gpllib directory -- libcom32gpl.a -- then you
> are subject to the GPL
Thank you very much for the clarification.

Cheers,

don