OpenJDK and JNI -- licensing
volker.simonis at gmail.com
Wed Jul 8 03:33:48 PDT 2009
Yes, I understand that conflict. But the HotSpot library libjvm.so
itself is build mostly from files which are pure GPL and some files
(in particular "jni.h") which are GPL + class path exception).
So how can "jni.cpp" (which is GPL only) include "jni.h" (which is GPL
+ class path) and finally be statically linked with other GPL only
files into a GPL-only "libjvm.so"???
On 7/8/09, Florian Weimer <fweimer at bfk.de> wrote:
> * Volker Simonis:
> > My only point was that I don't think that Sun's interpretation of
> > "linking", "derived work" and "classpath exception" is in accordance
> > with the FSF view of these terms, especially in the case of the
> > HotSpot shared library which is build from files licensed under both
> > "pure" GPL and GPL plus classpath exception.
> There are two conflicting lines of thoughts regarding GPLed program
> loaders: The first one says that loaded programs are not subject to
> the loader's GPL license. This is the stance taken by the Linux folks
> for their kernel. The second one says that the loaded program has to
> be GPLed as well. This one is sometimes cited in the Emacs Lisp
> context (meaning that anything which runs on Emacs has to be GPLed).
> So it's certainly a good idea for the copyright owners of such program
> loaders to clarify their position on this topic.
> Florian Weimer <fweimer at bfk.de>
> BFK edv-consulting GmbH http://www.bfk.de/
> Kriegsstraße 100 tel: +49-721-96201-1
> D-76133 Karlsruhe fax: +49-721-96201-99
More information about the discuss