Description of problem: The symlink /usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/include/jni.h is a dangling symlink and there are two problems with it: (1) The path contains "gcc-lib", while this should be "gcc" (pathnames with gcc-lib are only found in compat-gcc packages). This is the easy one... (2) The pathname contains a hardcoded "i386-redhat-linux", so it won't work on non-i386 systems, like x86_64. This is more difficult to solve, as the package is a noarch package, so maybe a %post script should fix this by doing a "ln -snf /usr/lib/gcc/*-redhat-linux/%{gccver}/include/jni.h %{_jvmdir}/%{sdkdir}/include/". I hope there is a more elegant method... On the original -26jpp package there was even another problem as the noarch package seemed to be built on x86_64, so there was /usr/lib64 in the symlink. Version-Release number of selected component (if applicable): 1.4.2.0-27jpp
Ouch, almost 1 year old... Furthermore, $rpm -q -f /usr/lib/gcc/i386-redhat-linux/3.4.3/include/jni.h libgcj-devel-3.4.5-2 So java-1.4.2-gcj-compat-devel should Requires: libgcj-devel
The component this request has been filed against is not planned for inclusion in the next update. The decision is based on weighting the priority and number of requests for a component as well as the impact on the Red Hat Enterprise Linux user-base: other components are considered having higher priority and the number of changes we intend to include in update cycles is limited.
Product Management has reviewed and declined this request. You may appeal this decision by reopening this request.