X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49BD8F0D.5010906@gmail.com> Date: Sun, 15 Mar 2009 23:28:13 +0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: gcc4-java: packaging error? References: <49BD3870 DOT 3030501 AT users DOT sourceforge DOT net> <49BD43BB DOT 7080808 AT gmail DOT com> <49BD7D85 DOT 2030701 AT users DOT sourceforge DOT net> In-Reply-To: <49BD7D85.2030701@users.sourceforge.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Yaakov (Cygwin/X) wrote: >> I do not know yet if the Eclipse Java compiler license is compatible with >> the Cygwin license, so for the moment I haven't shipped it in the distro. >> (OTOH it now looks like maybe I could have used it while building libgcj >> without needing to distribute it.) > > IANAL, but ecj is just a jar file; it isn't linked against cygwin, so as > long as its license allows for redistribution, how could it be > incompatible with Cygwin's license? It probably isn't, but making certain is just something I ran out of time for before the release. >> There are bugs in the java distro right now which I'll try and fix before >> the next major release (but not for the rapid-respin I'm liable to do first). > > So I see. I see that Debian builds gcj and all the java stuff > separately from the other gcc backends; maybe such a setup would be > helpful here as well? I'll take a look, thanks. cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/