Bug 1196994 - czmq zdigest test fails on bigendian
Summary: czmq zdigest test fails on bigendian
Alias: None
Product: Fedora
Classification: Fedora
Component: czmq
Version: 23
Hardware: Unspecified
OS: Linux
Target Milestone: ---
Assignee: Jose Pedro Oliveira
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ZedoraTracker PPCTracker
TreeView+ depends on / blocked
Reported: 2015-02-27 09:54 UTC by Jakub Čajka
Modified: 2016-12-20 13:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-12-20 13:17:55 UTC

Attachments (Terms of Use)
Partial fix (831 bytes, patch)
2015-02-27 09:54 UTC, Jakub Čajka
no flags Details | Diff

Description Jakub Čajka 2015-02-27 09:54:02 UTC
Created attachment 995957 [details]
Partial fix

build fails on bigendian machines due to zdigest test failure.


It is partially caused by not detecting endianess in configure script. In attachment is patch fixing this issue on all 64bit arches, but test still fails on s390(31bit), still looking in to it. Patch will need configure regeneration in specfile(or adding BR for autoconfigure should probably work too) as it modifies configure.ac.

I have sent attached patch to upstream at https://github.com/zeromq/czmq/pull/943

This affects all branches.

Comment 1 Jose Pedro Oliveira 2015-03-02 00:03:22 UTC
Hi Jakub,

Could you try to build czmq-2.2.0-5.fc23 for PPC and s390? The SRPM is available in http://koji.fedoraproject.org/koji/buildinfo?buildID=616924 .


Comment 2 Jakub Čajka 2015-03-03 14:58:17 UTC
Builds seem to pass now with latest version from fedora git. The issues on s390 that I have seen, were probably caused by my changes to packaging/build scripts. So it seems there is no issue now. 

Scratch builds:

You can do the scratch builds on secondary kojis too. 
From cli:
ppc-koji build --scratch f21 foo.src.rpm (replace "ppc" with s390 or arm(aarch64), for corresponding arch koji)

Could you please back-port this changes to all branches.

Thank you.

Comment 3 Jan Kurik 2015-07-15 14:28:56 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:

Comment 4 Fedora End Of Life 2016-11-24 11:30:09 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 5 Fedora End Of Life 2016-12-20 13:17:55 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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

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

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