Re: [Log4cplus-devel] License incompatibility

[Václav Z. <vha...@gm...>]

On 25 November 2013 13:15, Polhodzik Peter (ext) wrote:
> Hi,
>
>
>
> Is there a special reason that log4cplus is fine with different GNU GPL
> licensed files in the Apache licensed OS? On Apache site I read they are
> incompatible.
>
>
>
> GNU GPL v3 with exceptions, for example:
>
>
>
> \log4cplus-1.1.2\m4\ax_append_flag.m4
>
> \log4cplus-1.1.2\m4\ax_compiler_vendor.m4
>
> \log4cplus-1.1.2\m4\ax_pthread.m4
>
> \log4cplus-1.1.2\m4\ax_cflags_warn_all.m4
>
> \log4cplus-1.1.2\m4\ax_cflags_sun_option.m4
>
> \log4cplus-1.1.2\m4\ax_type_socklen_t.m4
>
> \log4cplus-1.1.2\m4\ax_cflags_gcc_option.m4
>
> \log4cplus-1.1.2\m4\ax_cflags_aix_option.m4

IANAL, so I am not sure if and what problem is there. The files
mentioned above are distributed with the log4cplus source so I think
the GPL side of things is covered and adhered to. The macros contain
an exception that removes the GPL coverage from the resulting
configure script. This email thread seems to support my view of the
licensing issue:
http://lists.gnu.org/archive/html/automake/2009-03/msg00031.html

I am not aware of any part of log4cplus binaries or headers that would
be covered by GPL, thus the resulting binary is not covered by GPL,
only by ASL 2.0 and by 2-BSD.

Whether or not ASL 2.0 is anyhow violated, I cannot tell. However I do
not think it is the case. You should probably ask a real IP lawyer
about this if you really need an authoritative answer.

-- 
VZ