The next step

Carl R. Witty
29 May 2001 16:24:11 -0700

"Manuel M. T. Chakravarty" <> writes:

> However, many libraries in the current hslibs and, judging
> from the discussion so far, many new libraries are not
> belonging to this core.  What is the problem if they are
> LGPL?  LGPL code can be linked into proprietary code without
> any problems.  There is lots of proprietary code being based
> on code generated by gcc and linked against its C library.

To link your code with LGPL code, you effectively must either provide
the user with object files for your code, or arrange for the LGPL code
to be contained in a shared library (the actual requirement is that
the user be able to modify the LGPL code and obtain a version of your
program that uses these modifications).  The former option is a
significant cost in terms of how annoying it is to distribute your
code.  I don't know if the latter is even possible -- can all the
Haskell implementations create shared libraries?

At any rate, while it is certainly possible to link proprietary code
with LGPL code, I wouldn't say that the combination is "without any

Carl Witty