From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id NAA06323; Mon, 6 Sep 2004 13:34:39 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id NAA07686 for ; Mon, 6 Sep 2004 13:34:37 +0200 (MET DST) Received: from kurims.kurims.kyoto-u.ac.jp (kurims.kurims.kyoto-u.ac.jp [130.54.16.1]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id i86BYZXa007285 for ; Mon, 6 Sep 2004 13:34:36 +0200 Received: from localhost (suiren.kurims.kyoto-u.ac.jp [130.54.16.25]) by kurims.kurims.kyoto-u.ac.jp (8.9.3p2-20030924/3.7W) with ESMTP id UAA02110; Mon, 6 Sep 2004 20:34:24 +0900 (JST) Date: Mon, 06 Sep 2004 20:34:20 +0900 (JST) Message-Id: <20040906.203420.68034706.garrigue@kurims.kyoto-u.ac.jp> To: skaller@users.sourceforge.net Cc: caml-list@inria.fr Subject: Re: [Caml-list] Announcing the OMake build system version 0.9.1 From: Jacques Garrigue In-Reply-To: <1094463492.3352.1061.camel@pelican.wigram> References: <7810902A-FF99-11D8-8747-000A958FF2FE@wetware.com> <20040906.113527.125105732.garrigue@kurims.kyoto-u.ac.jp> <1094463492.3352.1061.camel@pelican.wigram> X-Mailer: Mew version 4.0.64 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Miltered: at concorde with ID 413C4B4B.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; caml-list:01 jacques:01 sourceforge:01 2004:99 jacques:01 incompatible:01 gpled:01 gpl:01 distinctions:01 dlopen:01 gpl:01 statically:01 wwwfun:01 linked:01 compiler:01 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk From: skaller > On Mon, 2004-09-06 at 12:35, Jacques GARRIGUE wrote: > > > Looks like you make the classical confusion: > > 1) You have every right to use several (even incompatible) licenses in > > the same distribution (ocaml does it). The only restriction is that > > all code linked inside a GPLed tool must be provided under a > > GPL-compatible license. > > > So I don't see how the fact a tool is distributed under the GPL could > > limit your ability to use it (and improve it). > > > The only problem you might have is if you want to link omake itself > > with an existing library, > > By resting on unsustainable technical distinctions, > any usage is likely to expose the client to legal risk. > > What the heck does 'linkage' actually mean outside > of a Unix based C environment? How is it possible > that you can dlopen an GPL library without infection, > but if you statically link you're infected? Please, do not muddy the issue. We were talking about a standalone tool which is managing compilation (not even a compiler!) There is no ambiguity about linkage here, for the good reason that there is nothing to link to. Or will you tell me that using gnu make forces me to put all my software under the GPL! --------------------------------------------------------------------------- Jacques Garrigue Kyoto University garrigue at kurims.kyoto-u.ac.jp JG ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners