Stepan Kasal wrote:
On Tue, May 05, 2009 at 01:43:59PM -0400, Bill Nottingham wrote:
> Andrew Overholt (overholt(a)redhat.com) said:
>> * Andrew Haley <aph(a)redhat.com> [2009-05-05 10:51]:
>>> The best defaults for koji are probably gcj on non-x86 machines and
>>> openjdk on x86 machines.
>> If I say "yum install java-devel" what gets installed? How is it
> Via the comps file. The current java development group is attached. By
> default, installing the group gets you the 'mandatory' and 'default'
> The comps file does not have arch-specific bits, so doing gcj on
> non-x86 and openjdk on x86 isn't really practical, without a lot
> of metapackages.
this explanation sort of confuses me. The current situation really
*is* what Andrew Haley proposed.
I guess that though the comps file does not have arch-specific bits,
the installation is determined by arch-specific dependencies in the
That was exactly what has brought my attention to this:
the differences between the two java's (e.g. that jni.h is installed
to the default include path by gcj but not by openjdk, different
javadocs) make the good old generic
very problematic, so I had to change it to
Well, my package builds fine with gcj and my conscience is clear as I
have reported this, so all is fine. :-)
Sure, but it would make much more sense to look for jni.h in the right
place: then it would build with either. I would like to move jni.h out
of the compiler's default include path, but then God only knows what
else would break.