Bug 1147415

Summary: add proper check for valgrind availability into buildsystem
Product: [Fedora] Fedora Reporter: Dan Horák <dan>
Component: libsecretAssignee: Kalev Lember <kalevlember>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: debarshir, kalevlember, stefw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1147446 (view as bug list) Environment:
Last Closed: 2016-07-19 12:10:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 467765, 1147446    

Description Dan Horák 2014-09-29 08:40:44 UTC 
libsecret started to use system valgrind headers after bug #1141474, but it fails on arches where valgrind is missing (currently s390). There is some support for optional valgrind in the code, but proper check in configure is missing, so it is enable unconditionally. I have workarounded it in libsecret-0.18-6.fc21, but a better solution is needed.


Version-Release number of selected component (if applicable):
libsecret-0.18-5.fc21
Comment 1 Jaroslav Reznik 2015-03-03 16:19:57 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 2 Fedora End Of Life 2016-07-19 12:10:19 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.