Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1377790

Summary: BUG: valgrind is broken/missing on MIPS
Product: [Fedora] Fedora Reporter: Michal Toman <michal.toman>
Component: libseccompAssignee: Paul Moore <pmoore>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: michal.toman, pmoore
Target Milestone: ---   
Target Release: ---   
Hardware: mips64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:40:49 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: 1242747    
Attachments:
Description Flags
No-valgrind-on-MIPS.patch none

Description Michal Toman 2016-09-20 15:22:31 UTC
Created attachment 1202944 [details]
No-valgrind-on-MIPS.patch

Description of problem:
We are trying to bring Fedora to MIPS platform and this requires updating libseccomp SPEC not to require valgrind. We have no working valgrind builds on MIPS at this moment.

Actual results:
Build fails because valgrind is required.

Expected results:
Build passes.

Additional info:
Attaching dist-git patch. It would be nice to have this in F25 as well.

Comment 1 Paul Moore 2016-09-20 15:29:20 UTC
(In reply to Michal Toman from comment #0)
> We have no working valgrind builds on MIPS at this moment.

Are you planning to have valgrind working on MIPS?

Comment 2 Michal Toman 2016-09-20 15:42:25 UTC
For 32-bit it is unlikely since upstream lacks support for FPXX floating point which we are building at this moment.

For 64-bit all the bits should be upstream. The valgrind package even builds but the resulting binaries do not work - they either segfault immediately or enter an endless loop. We want to fix this and have a working valgrind but I was not able to find the problem so far.

Comment 3 Paul Moore 2016-09-20 15:46:51 UTC
(In reply to Michal Toman from comment #2)
> For 32-bit it is unlikely since upstream lacks support for FPXX floating
> point which we are building at this moment.

If we are never going to support valgrind on 32-bit MIPS then I think it is probably reasonable to add the BuildRequires exception for 32-bit.

> For 64-bit all the bits should be upstream. The valgrind package even builds
> but the resulting binaries do not work - they either segfault immediately or
> enter an endless loop. We want to fix this and have a working valgrind but I
> was not able to find the problem so far.

Is there a BZ for this problem?  I would prefer to leave the valgrind BuildRequires for 64-bit MIPS; disabling tests isn't something I like to do unless there is no other way.

Comment 4 Fedora End Of Life 2017-02-28 10:20:19 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 5 Fedora End Of Life 2018-05-03 08:28:03 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2018-05-29 11:40:49 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.

Comment 7 Red Hat Bugzilla 2023-09-12 01:09:44 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days