Bug 1033902 - FTBFS on big endians
FTBFS on big endians
Product: Fedora
Classification: Fedora
Component: xfsprogs (Show other bugs)
s390x Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Eric Sandeen
Fedora Extras Quality Assurance
Depends On:
Blocks: ZedoraTracker
  Show dependency treegraph
Reported: 2013-11-24 04:12 EST by Dan Horák
Modified: 2013-11-25 18:18 EST (History)
1 user (show)

See Also:
Fixed In Version: xfsprogs-3.2.0-0.2.alpha2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-11-25 18:18:08 EST
Type: Bug
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 Dan Horák 2013-11-24 04:12:22 EST
xfsprogs-3.2.0-0.1.alpha1.fc21 fails to build on big endian arches (s390, ppc), please sync with RHEL-7 package. For full logs see for example http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1269837 and http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=1542535

Version-Release number of selected component (if applicable):
Comment 1 Eric Sandeen 2013-11-25 11:29:29 EST
> crc32c: 100 self tests failed

It'll be fixed shortly in -alpha2:

commit b2dbd6a9a2df5099882bdfc068caa76cf334c99a
Author: Eric Sandeen <sandeen@redhat.com>
Date:   Sat Oct 5 02:20:03 2013 +0000

    xfsprogs: fix crc32 build on big endian
    While kernelspace can test #ifdef __LITTLE_ENDIAN, this
    doesn't work in userspace.  __LITTLE_ENDIAN is defined -
    as is __BIG_ENDIAN.
    So we build on all boxes as __LITTLE_ENDIAN, and the
    self-test (thankfully!) fails on big endian boxes.
    Fix this by testing __BYTE_ORDER values.
    And add an else which should never be hit, but just in case...
    Signed-off-by: Eric Sandeen <sandeen@redhat.com>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>
    Signed-off-by: Rich Johnston <rjohnston@sgi.com>
Comment 2 Eric Sandeen 2013-11-25 18:18:08 EST
Should be good in Rawhide, please reopen if not.



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