libgcj linking and licensing issues

[Jim Plak <jjplak at yahoo dot com>]

Hi
 
After having spent several hours looking at all the
web sites and messages on the GPL with the LIBGCJ (and
LIBGCC) special exception I still have a few
questions.
 
Background: Commerical developer of Java library that
would like to destribute native version with C
interface as a Shared Object on several Unix variants.
Compiling with GCJ (from GCC 4.0.0) works great, CNI
is not problem, etc.
 
Question 1:
Based on the special exception I know if I statically
link with libgcj (and libgcc) I'm OK. I found,
however, that building a shared object (using -shared)
that statically links libgcj and libgcc was somewhat
difficult. I tried -shared and -static which simply
resulted in the same result as if -static were not
there. I tried -shared and -static-libgcc which pulled
libgcc into the result but not libgcj. In the end I
had to modify libgcj.spec, replacing -lgcj with
/usr/local/lib/libgcj.a. This produced the desired
result but it is unclear to me if this is the
"correct" way to do such a thing. Thoughts?
 
Question 2: 
As an alternative to the results from Question 1 I
would also like to ship the library with dynamic links
to libgcj.so and libgcc.so. Can I do this? Can I also
ship the actual libgcj.so and libgcc.so binaries on
which the library will depend?
 
Thanks
Jim Plak




		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new Resources site
http://smallbusiness.yahoo.com/resources/