Bug 163686 - Wrong symlink to jni.h in java gcj compat package
Wrong symlink to jni.h in java gcj compat package
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: java-1.4.2-gcj-compat (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Thomas Fitzsimmons
: EasyFix
Depends On:
  Show dependency treegraph
Reported: 2005-07-20 07:07 EDT by Jos Vos
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-09 18:17:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jos Vos 2005-07-20 07:07:53 EDT
Description of problem:

The symlink /usr/lib/jvm/java-1.4.2-gcj- 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
%{_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):
Comment 1 Rex Dieter 2006-06-06 13:24:39 EDT
Ouch, almost 1 year old... 

$rpm -q -f /usr/lib/gcc/i386-redhat-linux/3.4.3/include/jni.h
So java-1.4.2-gcj-compat-devel should
Requires: libgcj-devel
Comment 2 RHEL Product and Program Management 2006-10-09 18:09:08 EDT
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.
Comment 3 RHEL Product and Program Management 2006-10-09 18:17:42 EDT
Product Management has reviewed and declined this request.  You may appeal this
decision by reopening this request. 

Note You need to log in before you can comment on or make changes to this bug.