-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dave Korn wrote: > IIUC, GCJ accepts both java source (.java) and byte code (.class) files and > compiles them to native assembly. In order to compile .java files to > bytecode, it relies on the Eclipse Java compiler front-end.
OK, this is something new with gcc-4.3; I wasn't aware of that until now. > 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? > 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? Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkm9fYUACgkQpiWmPGlmQSOrwACfUqMRymGmjYn3R9j0tfH/3gtA EqwAoNTFHPGY65w5j+SwnvaMRUueYe5C =p8RB -----END PGP SIGNATURE----- -- 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/
