Bug 509471 - Build-classpath script does not detect jpcap library (a JNI Lib)
Build-classpath script does not detect jpcap library (a JNI Lib)
Product: Fedora
Classification: Fedora
Component: jpackage-utils (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Deepak Bhole
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-07-02 20:57 EDT by Patrick Dignan
Modified: 2009-07-03 09:55 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-03 09:55:50 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 Patrick Dignan 2009-07-02 20:57:33 EDT
Description of problem: The build-classpath script does not detect the jpcap library.  It may not even detect JNI libraries in general...

Version-Release number of selected component (if applicable):

How reproducible: 100%

Steps to Reproduce:
1.Use the $(build-classpath jpcap) macro in a spec file.
Actual results: A blank classpath

Expected results: A classpath with /usr/lib/jpcap/jpcap.jar in it

Additional info:
Comment 1 Deepak Bhole 2009-07-03 09:55:50 EDT
build-classpath will not work in this case. This is expected behaviour actually. Per the guidelines[1]:

"JAR files that require JNI shared objects  ........ <snip> ......... If you are depending on a JNI-using JAR file, you'll need to add it manually -- build-classpath will not find it. "

1: http://fedoraproject.org/wiki/Packaging/Java#Packaging_JAR_files_that_use_JNI

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