RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 606308 - oprofile-jit: libjvmti_oprofile.so is not built
Summary: oprofile-jit: libjvmti_oprofile.so is not built
Keywords:
Status: CLOSED DUPLICATE of bug 463223
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: oprofile
Version: 6.0
Hardware: All
OS: All
low
high
Target Milestone: rc
: ---
Assignee: William Cohen
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks: 463393
TreeView+ depends on / blocked
 
Reported: 2010-06-21 11:54 UTC by Hendrik Brueckner
Modified: 2011-05-13 12:51 UTC (History)
2 users (show)

Fixed In Version: oprofile-0.9.6-7.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-21 12:57:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Hendrik Brueckner 2010-06-21 11:54:41 UTC
Description of problem:

The libjvmti_oprofile.so is not built and packaged in the oprofile-jit package. Without the libjvmti_oprofile.so library, performance profiling is not available for Java programs.

The lib is not built because the in the %prep section of the rpm specfile, the openjdk-include.tar.gz tarball containing required header files are not extracted.  The oprofile configure script does not find the required jvmti.h file and, therefore, the lib is built and packaged.

Fix proposal: extract the the openjdk-include.tar.gz during the %prep step of the rpm build. For example, add the following into the %prep section (after the first %setup):
%setup -T -D -a 1


Version-Release number of selected component (if applicable):
oprofile-0.9.6-5.el6.src.rpm

How reproducible:
always

Steps to Reproduce:
check the file list of the oprofile-jit if "/usr/lib64/oprofile/libjvmti_oprofile.so" is included
  
Actual results:
The lib is not included.

Expected results:
"/usr/lib64/oprofile/libjvmti_oprofile.so" is included.

Additional info:
The problem has been found on s390x, but it might exist on other architectures.

Comment 2 RHEL Program Management 2010-06-21 12:23:21 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 William Cohen 2010-06-21 12:57:39 UTC
This should be fixed in oprofile-0.9.6-7.el6.

*** This bug has been marked as a duplicate of bug 463223 ***

Comment 4 Georg Markgraf 2010-06-21 13:21:42 UTC
I guess that fix can be expected with snap7 - right?


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