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

Bug 926374

Summary: protobuf: Does not support aarch64 in f19 and rawhide
Product: [Fedora] Fedora Reporter: Dennis Gilmore <dennis>
Component: protobufAssignee: Lev Shamardin <shamardin>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cse.cem+redhatbugz, mizdebsk, shamardin, sochotni
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: protobuf-2.5.0-3.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-14 04:37:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 922257    
Description Flags
Proposed patch none

Description Dennis Gilmore 2013-03-23 16:08:47 UTC
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in 
autoconf 2.69.  protobuf appears to use an earlier version of 
autoconf, preventing its being built.  This can be fixed in of three ways (In order of preference):

1. Work with upstream to migrate the package to autoconf 2.69.

2. Rerun autoconf or autoreconf in %prep or %build prior to running 

3. Apply the patch at
which updates config.guess and config.sub to recognize aarch64.

Comment 1 Conrad Meyer 2013-04-27 21:29:15 UTC
Protobuf already uses (2), I've bumped the revision number and started a build in rawhide:

I think this means we just need to bump / rebuild in all branches with autoconf >= 2.69.

Comment 2 Conrad Meyer 2013-04-27 21:33:37 UTC
In fact, this isn't even needed in rawhide, 2.5.0 was already built with autoconf 2.69:

It's actually not even needed in F-18 (2.4.1) either:

Only F-17 was built with autoconf < 2.69 (2.68). Do we care about getting aarch64 into old-stable? I'm inclined to NOTABUG.

Comment 3 Stanislav Ochotnicky 2013-04-29 06:47:49 UTC
I am reopening so we don't lose track of this because AARCH64 is also affected by bug 955577. Upstream dropped support for *a lot* of archs suddenly in 2.5.0. Need to look into implementing their atomic operations using GCC atomic ops.

Comment 4 Conrad Meyer 2013-04-29 14:40:43 UTC
Looks like they support ARM 32-bit little-endian, as well as ppc32, but not 64-bit variants of either:

Comment 5 Conrad Meyer 2013-04-29 14:41:19 UTC
If you have the hardware to test on, upstream is happy to take patches:

Comment 6 Stanislav Ochotnicky 2013-05-06 13:28:13 UTC
Created attachment 744146 [details]
Proposed patch

I have created a patch that uses generic gcc atomic operations on architectures that are not supported as first-class citizens. The patch has been submitted upstream as well[1]


Comment 7 Conrad Meyer 2013-05-06 15:54:07 UTC
Awesome! Have you tested the library on any of these platforms? The google bug just mentions building.

Comment 8 Stanislav Ochotnicky 2013-05-09 14:45:24 UTC
(In reply to comment #7)
> Awesome! Have you tested the library on any of these platforms? The google
> bug just mentions building.

I have tested clementine & muble work, but I don't know for sure which parts of protobuf they use. I would be surprised if they used these atomic functions though so it doesn't tell us much about my patch except it doesn't break working stuff :-)

Comment 9 Conrad Meyer 2013-05-09 15:45:45 UTC
Sounds good to me.

Scratch build in rawhide succeeded:

Pushing to branches that have 2.5.0 now.

Comment 11 Fedora Update System 2013-05-09 17:50:11 UTC
protobuf-2.5.0-3.fc19 has been submitted as an update for Fedora 19.

Comment 12 Fedora Update System 2013-05-10 15:35:14 UTC
Package protobuf-2.5.0-3.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing protobuf-2.5.0-3.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 13 Fedora Update System 2013-05-14 04:37:47 UTC
protobuf-2.5.0-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.