Bug 1295350 - [purple-telegram] fails to build on ppc64 due to endianness issue
Summary: [purple-telegram] fails to build on ppc64 due to endianness issue
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: purple-telegram
Version: 24
Hardware: ppc64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jiri Eischmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: PPCTracker
TreeView+ depends on / blocked
 
Reported: 2016-01-04 08:59 UTC by Rafael Fonseca
Modified: 2016-08-11 14:43 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2016-08-11 14:43:12 UTC


Attachments (Terms of Use)

Description Rafael Fonseca 2016-01-04 08:59:01 UTC
Description of problem: purple-telegram fails to build on ppc64 with the following endianness issue:

bin/generate -g autocomplete-header auto/scheme.tlo > auto/auto-autocomplete.h || ( rm auto/auto-autocomplete.h && false )
generate: generate.c:2800: parse_tlo_file: Assertion `get_int () == 0x3a2f9be2' failed.
generate: generate.c:2800: parse_tlo_file: Assertion `get_int () == 0x3a2f9be2' failed.
generate: generate.c:2800: parse_tlo_file: Assertion `get_int () == 0x3a2f9be2' failed.
generate: generate.c:2800: parse_tlo_file: Assertion `get_int () == 0x3a2f9be2' failed.

Printing the output of get_int() gives: 0xe29b2f3a


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


How reproducible: always on koji-ppc64.


Additional info: fails on f22, f23 and rawhide.

Comment 1 Dan Horák 2016-01-04 09:52:31 UTC
bug 1138804 (telegram-cli) is likely related

Comment 2 Jan Kurik 2016-02-24 14:13:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 3 Rafael Fonseca 2016-08-11 14:43:12 UTC
purple-telegram >= 1.2.5-1 builds successfully, so closing this bug.


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