Bug 672854

Summary: Broken jni.h symlink in java-1.4.2-gcj-compat-1.4.2.0-27jpp
Product: Red Hat Enterprise Linux 4 Reporter: Mattias Ellert <mattias.ellert>
Component: java-1.4.2-gcj-compatAssignee: Rodney Russ <rruss>
Status: CLOSED WONTFIX QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.8   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 15:57:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mattias Ellert 2011-01-26 15:35:48 UTC 
Description of problem:

java-1.4.2-gcj-compat-1.4.2.0-27jpp installs a symlink:

/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/include/jni.h →
/usr/lib/gcc-lib/i386-redhat-linux/3.4.3/include/jni.h

However, the file installed by gcc-3.4.6-11.el4_8.1 is located at:

/usr/lib/gcc/i386-redhat-linux/3.4.3/include/jni.h

This means that the symlink installed by java-1.4.2-gcj-compat is broken.

Version-Release number of selected component (if applicable):
java-1.4.2-gcj-compat-1.4.2.0-27jpp
gcc-3.4.6-11.el4_8.1

How reproducible:
Always

Additional info:
I don't know if it is the symlink that points to the wrong place or it is the file itself that is installed in the wrong place.
Comment 1 Mattias Ellert 2011-01-26 18:15:52 UTC 
This might be tricky to fix since java-1.4.2-gcj-compat is a noarch package and the destination of the symlink is architecture dependent...
Comment 2 Jiri Pallich 2012-06-20 15:57:01 UTC 
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.