ABCD <[email protected]> posted [email protected], excerpted below, on Fri, 23 Jan 2009 22:45:49 -0500:
> I'm not certain that this is the *easiest* method, but I've found > installing dev-java/gcj-jdk temporarily before building icedtea6 (note > that sys-devel/gcc must have USE=gcj for gcj-jdk to build) works well, > as gcj-jdk meets the requirement for virtual/gnu-classpath-jdk, which > means that icedtea6 will not depend on itself. > > Using gcj-jdk, I managed to build icedtea6 without ever having had > sun-jdk installed on this system. This has worked both on my amd64 > system, as well as my x86 system. Iced-tea on amd64 has had problems, see the writeup in flameeyes' blog from a month or so ago (maybe a couple by now...). That's the latest I've read until now. Back then, at least with a no-multilib amd64 profile, it wouldn't build very easily, and AFAIK not at all without first installing the still non-freedomware licensed sun version in ordered to build icedtea. If what you say is correct, that's no longer the case -- only USE=gcj gcc and gcj-jdk are needed. If so, that's a very good thing, and it's relatively new. One thing's for sure, various devs, both Gentoo and upstream, have been putting some pretty hard work into it to get it working without depending on non-freedomware somewhere along the line. If it's not working now (I don't know, but from what you say it is =:^), it should be working soon, and the devs deserve MAJOR kudos for getting it working! Looks like I should look into it again myself, one of these days. It has been awhile since I had Java, since I've been freedomware-only for quite awhile now, and amd64 no-multilib for... probably over a year now. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
