Bug 1155082

Summary: qpid-cpp FTBFS on AArch64, assumes Big Endian on PPC
Product: [Fedora] Fedora Reporter: Marcin Juszkiewicz <mjuszkie>
Component: qpid-cppAssignee: Darryl L. Pierce <dpierce>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dpierce, iboverma, jose.p.oliveira.oss, nsantos, pbrobinson, tross
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-29 17:53:46 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: 922257, 1051573    
Attachments:
Description Flags
patch + spec changeset none

Description Marcin Juszkiewicz 2014-10-21 11:11:34 UTC 
Created attachment 948887 [details]
patch + spec changeset

Description of problem:

qpid-cpp fails to build on AArch64 architecture. It's set of checks for word size and endianness does not cover it.

Also it always assumes that PowerPC is big endian which is not true for ppc64le.

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

0.30-3

How reproducible:

always

Steps to Reproduce:
1. do a build for aarch64
2.
3.

Actual results:

In file included from /builddir/build/BUILD/qpid-cpp-0.30/src/qpid/legacystore/jrnl/rec_hdr.h:38:0,
                 from /builddir/build/BUILD/qpid-cpp-0.30/src/qpid/legacystore/jrnl/deq_hdr.h:37,
                 from /builddir/build/BUILD/qpid-cpp-0.30/src/qpid/legacystore/jrnl/deq_rec.h:45,
                 from /builddir/build/BUILD/qpid-cpp-0.30/src/qpid/legacystore/jrnl/deq_rec.cpp:33:
/builddir/build/BUILD/qpid-cpp-0.30/src/qpid/legacystore/jrnl/jcfg.h:49:2: error: #error endian?
 #error endian?
  ^

Expected results:

package builds

Additional info:

patch submitted upstream for discussion
Comment 1 Peter Robinson 2015-01-29 17:53:46 UTC 
I think this is now fixed