Hello Peter, Wednesday, November 15, 2006, 9:08:16 AM, you wrote:
>>> I guess I am trying to sort out the goals for the task and I tend >>> toward the relatively aesthetic option of creating a stand-alone GHC >>> compiler running on Windows (i.e., no extra tools shipped). In >>> addition to being aesthetic, mingw is GPL-licensed. >> >> this is again more aesthetic than real problem - code compiled by >> GPL'ed tools is not GPL'ed > True. I should add a few notes: I did not mean to imply that merely > distributing mingw with GHC in the same package would create a > licensing problem; I also think I overstated it a bit: mingw is > public domain but mingw development tools are GPL--o.k. to use, of > course--but the libraries (libgcc, libgcov) are LGPL, so static > linkage to the libraries makes the resulting code LGPL. if this is true, this means a problem for existing GHC that creates mingw-compiled executables. but for ghc that will use MS libraries coming with CL, this is not a problem again - we can use mingw-compiled perl and other *tools* because this don't mean that resulting program will use mingw *libs* -- Best regards, Bulat mailto:[EMAIL PROTECTED] _______________________________________________ Cvs-ghc mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-ghc
