Bug 672854 - Broken jni.h symlink in java-1.4.2-gcj-compat-1.4.2.0-27jpp
Summary: Broken jni.h symlink in java-1.4.2-gcj-compat-1.4.2.0-27jpp
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: java-1.4.2-gcj-compat
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rodney Russ
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-26 15:35 UTC by Mattias Ellert
Modified: 2012-06-20 15:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 15:57:01 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


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