To me this seem the same as linking to glibc which is an LGLP lib and a lib which just about every app on linux links to. Surely even apr links to it right?
This can also be seen a linking against hibernate, but not distributing it. On Mon, Dec 21, 2015 at 1:10 PM, Daniel Kulp <[email protected]> wrote: > >> On Dec 21, 2015, at 1:08 PM, Clebert Suconic <[email protected]> >> wrote: >> >> In particular, in org_apache_activemq_artemis_jlibaio_LibaioContext.c, >> I see right at the top: >> >> #ifndef _GNU_SOURCE >> // libaio, O_DIRECT and other things won't be available without this define >> #define _GNU_SOURCE >> #endif >> >> >> this has nothing to do with LGPL licenses.. or even libaio on this >> instance.. That's how you enable O_DIRECT, with O_DIRECT being a Linux >> extension non conformant with POSIX. the header is there for any >> source code using it. >> >>> …linked to libraries that are LGPL and only LGPL, which is not allowed per >>> ASF policy. >>> >> >> Dynamic linked.. it doesn't not include libaio. > > But is still REQUIRED for building the library… Thus, the library still has > a REQUIRED dependency on a LGPL’d library to work. Thus, it must be > optional and the user must take explicit actions to enable it during build > and runtime. > > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > -- Hiram Chirino Engineering | Red Hat, Inc. [email protected] | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino
