| 1 |
On Tue, 2007-11-27 at 16:39 +0200, Petteri Räty wrote: |
| 2 |
> gnu-classpath should have ./configure switches for forcing the compiler. |
| 3 |
|
| 4 |
It has --with-ecj and --with-ecj-jar=; unfortunately it ignored them, |
| 5 |
and continued to use the javac |
| 6 |
in /etc/java-config-2/current-system-vm/bin. That's something their |
| 7 |
configure was picking up for itself, as its not something that the |
| 8 |
ebuild is supplying. |
| 9 |
|
| 10 |
When I raised this with my friends in the classpath community, people |
| 11 |
said that they didn't bother to test whether their product would build |
| 12 |
with Sun javac 1.5. I was agog, but their response was "well, it builds |
| 13 |
with icedtea". |
| 14 |
|
| 15 |
Ignoring that topic for a minute, I just tried installing a 1.6 Sun JDK |
| 16 |
(it wasn't available last time I worked on this) It's possible that |
| 17 |
classpath will build with Sun javac 1.6 and force switched the system VM |
| 18 |
to it. The Java compile passed.... |
| 19 |
|
| 20 |
[The original question remains, however: how does one force a |
| 21 |
Gentoo Java ebuild to require a specific compiler or version |
| 22 |
thereof?] |
| 23 |
|
| 24 |
...but then some of the C building crapped out, some gsteamer related |
| 25 |
file not finding a GDK header. Bah. So I did USE-gstreamer to get it to |
| 26 |
fly, but that then broke the ebuild which has |
| 27 |
|
| 28 |
dodoc README.gsteamer |
| 29 |
|
| 30 |
with that removed the ebuild passed at last, and jamvm 1.5.0 (which was |
| 31 |
the whole point of the exercise) built fine with a straight forward rev |
| 32 |
bump of its existing ebuild. |
| 33 |
|
| 34 |
So as far as dev-java/gnu-classpath is concerned, a 0.96.1 ebuild will |
| 35 |
need to depend on Java >= 1.6 |
| 36 |
|
| 37 |
AfC |
| 38 |
Sydney |
| 39 |
|
| 40 |
[Actually, I did USE="-gstreamer -gtk -cairo -alsa" as well, but that's |
| 41 |
because I don't much care about Swing] |
Archives