Re: [gentoo-java] Using a compiler other than that configured at system level in an ebuild

[Andrew Cowie <andrew@operationaldynamics.com>]

[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]

On Tue, 2007-11-27 at 16:39 +0200, Petteri Räty wrote:
> gnu-classpath should have ./configure switches for forcing the compiler.

It has --with-ecj and --with-ecj-jar=; unfortunately it ignored them,
and continued to use the javac
in /etc/java-config-2/current-system-vm/bin. That's something their
configure was picking up for itself, as its not something that the
ebuild is supplying.

When I raised this with my friends in the classpath community, people
said that they didn't bother to test whether their product would build
with Sun javac 1.5. I was agog, but their response was "well, it builds
with icedtea".

Ignoring that topic for a minute, I just tried installing a 1.6 Sun JDK
(it wasn't available last time I worked on this) It's possible that
classpath will build with Sun javac 1.6 and force switched the system VM
to it. The Java compile passed....

        [The original question remains, however: how does one force a
        Gentoo Java ebuild to require a specific compiler or version
        thereof?]

...but then some of the C building crapped out, some gsteamer related
file not finding a GDK header. Bah. So I did USE-gstreamer to get it to
fly, but that then broke the ebuild which has 

        dodoc README.gsteamer

with that removed the ebuild passed at last, and jamvm 1.5.0 (which was
the whole point of the exercise) built fine with a straight forward rev
bump of its existing ebuild.

So as far as dev-java/gnu-classpath is concerned, a 0.96.1 ebuild will
need to depend on Java >= 1.6

AfC
Sydney

[Actually, I did USE="-gstreamer -gtk -cairo -alsa" as well, but that's
because I don't much care about Swing]


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]