Hi Joachim, On Tue, May 14, 2019 at 04:32:34PM +0200, Joachim Durchholz wrote:

The usual understanding of the LGPL enforces the LGPL license only on the lib-gmp code itself and any modifications you make to it, not on any other parts of the code.

if you follow the LGPL strictly - which I think almost nobody does - you also have to provide a development kit for you application, that users can relink your application with newer versions of the lib-gmp. Greetings, Daniel

Am 14.05.19 um 17:21 schrieb Daniel Trstenjak:

Hi Joachim,

On Tue, May 14, 2019 at 04:32:34PM +0200, Joachim Durchholz wrote:

...

The usual understanding of the LGPL enforces the LGPL license only on the lib-gmp code itself and any modifications you make to it, not on any other parts of the code.

if you follow the LGPL strictly - which I think almost nobody does - you also have to provide a development kit for you application, that users can relink your application with newer versions of the lib-gmp.

Mmm... sort-of. You have to make sure that people can take lib-gmp, change it, and relink your application with it. A reference to a standard build environment should be enough to fulfil that requirement, though it can become a bit more difficult if you have packaging steps after linking.

Most of the builds use a system or packaged libgmp of some variety, so it's not even bundled with ghc. (This includes Windows builds, using the package from msys2.)

Windows uses a statistically linked gmp built from source during the ghc bootstrap. It does not use libgmp from msys2. The difficulty here is that Haskell programs should work regardless of if you're running in msys2 or not. Compared to other languages that are dynamically linked ghc has no "runtime libraries". You'd have to ship libgmp with every application you make. On Tue, May 14, 2019, 19:47 Brandon Allbery wrote:

Most of the builds use a system or packaged libgmp of some variety, so it's not even bundled with ghc. (This includes Windows builds, using the package from msys2.)

On Tue, May 14, 2019 at 2:42 PM Joachim Durchholz wrote:

...

...

Hi Joachim,

On Tue, May 14, 2019 at 04:32:34PM +0200, Joachim Durchholz wrote:

...

The usual understanding of the LGPL enforces the LGPL license only on

Am 14.05.19 um 17:21 schrieb Daniel Trstenjak: the

...

...

lib-gmp code itself and any modifications you make to it, not on any other parts of the code.

if you follow the LGPL strictly - which I think almost nobody does - you also have to provide a development kit for you application, that users can relink your application with newer versions of the lib-gmp.

Mmm... sort-of. You have to make sure that people can take lib-gmp, change it, and relink your application with it. A reference to a standard build environment should be enough to fulfil that requirement, though it can become a bit more difficult if you have packaging steps after linking. _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

-- brandon s allbery kf8nh allbery.b@gmail.com _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.