Bug 598863 - self-test fails
self-test fails
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libgcrypt (Show other bugs)
All Linux
low Severity high
: rc
: ---
Assigned To: Tomas Mraz
BaseOS QE Security Team
Depends On:
  Show dependency treegraph
Reported: 2010-06-02 04:47 EDT by Ondrej Moriš
Modified: 2010-06-02 05:26 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-02 05:06:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Output of 'make check'. (5.66 KB, application/octet-stream)
2010-06-02 04:47 EDT, Ondrej Moriš
no flags Details

  None (edit)
Description Ondrej Moriš 2010-06-02 04:47:57 EDT
Created attachment 418958 [details]
Output of 'make check'.

Description of problem:

Self-test provided with libgcrypt package fails due to failing test 'basic'. See attached output for further details. 

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


How reproducible:


Steps to Reproduce:

1. build source (rpmbuild -bc ~/rpmbuild/SPEC/libgcrypt.spec)
2. execute self-test (make -C ~/rpmbuild/BUILD/libgcrypt-1.4.5/ check)
Actual results:

libgcrypt selftest: binary  (0): No such file or directory (/root/rpmbuild/BUILD/libgcrypt-1.4.5/src/.libs/.libgcrypt.so.11.hmac)
running self-test failed
FAIL: basic

Expected results:

PASS: basic

Additional info:

Upstream self-test works fine (all tests pass). High severity has been set since failing self-test may indicate corrupted component and there are a lot of packages depending on this one.
Comment 1 Tomas Mraz 2010-06-02 05:06:59 EDT
Nope, this is not a bug.
Just run 'fipshmac src/.libs/libgcrypt.so.??'
before the make check.
See what %check section of libgcrypt.spec does.
Comment 2 Ondrej Moriš 2010-06-02 05:26:18 EDT
Great, thanks for your prompt answer. Sorry for opening this bug.

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