------- Comment #2 from tromey at gcc dot gnu dot org 2007-01-26 02:23 -------
FWIW I don't think we want to fail outright if no suitable gcj is found.
The whole business with compiling and installing ecj.jar is a convenience,
not a strict necessity. The user can always make his own ecj1 "somehow"
(e.g, I use a shell script).
So one idea would be to look for a gcj for the build machine, and if not
found, disable compilation of ecjx.
What do you think?
--
tromey at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-01-26 02:23:25
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30591
