🚀 go-pugleaf

In article <MIKE.90Mar28135129@turing.cs.unm.edu> mike@unmvax.cs.unm.edu writes:
> ... [In order to get around the copyleft on libg++] ...
>Finally, note that this is really academic.  All you have to do is
>distribute a bunch of .o's and aggregate them with the library.
>Distribute the source to the library and not your .o's, and supply
>instructions to link the result.

Watch out! The problem here is that you need the header files for libg++ to
compile your code. Since these header files are source code, compiling your
C programs and including them forces your code under the copyleft! Thus,
source for your .o's must be distributed.

I hope we can get around this some day, since the libraries are as
intrinsic to the use of g++ as the compiler itself. If you don't modify
the libraries but just use them as is, why is this any different (from
the point of view of the FSF) than using the compiler as is?

kurt
-- 
Kurt Baudendistel --- GRA
Georgia Tech, School of Electrical Engineering, Atlanta, GA  30332
internet: baud@eedsp.gatech.edu         uucp: gatech!gt-eedsp!baud