[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

default JVM / future of gcj



Hi folks,

after the recent discussions about FTBFS due to gcj, I would like to
discuss the future of gcj in general here. The thread at [1] brings it
pretty much to the point I think, while gcj will not go away, there is
basically no further development to be expected upstream. Together with
the (now) increasing development of the language, Java 8 got released
just two weeks ago, the usefulness of gcj as a JVM is IMHO questionable.
I think currently there is no other option besides OpenJDK. I understood
that gcj is still needed to build OpenJDK-6/-7, but I currently see no
practical use for it beyond that.

The OpenJDK-8 upstream source code seems to have some *BSD support, but
due to some problems I cannot try to build it on kFreeBSD right now. The
question now is how we can proceed? I think it is important to improve
the OpenJDK availability in kFreeBSD and slowly think about phasing out
gcj all together (if possible).
I like to help where possible, but I am neither DM nor DD and so far I
do not have experience in building OpenJDK. So I am absolutely not sure
what I can do right now.

P.S.: I only sent this message to -bsd as the problem is largely the
specific kFreeBSD situation and I did not want pollute the -java ML.

[1] http://gcc.gnu.org/ml/gcc/2013-11/msg00153.html
-- 
Best Regards
Jan Henke

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: