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 http://ausil.fedorapeople.org/aarch64/protobuf/protobuf-aarch64.patch
which updates config.guess and config.sub to recognize aarch64.
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.
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.
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.
Looks like they support ARM 32-bit little-endian, as well as ppc32, but not 64-bit variants of either:
If you have the hardware to test on, upstream is happy to take patches:
Created attachment 744146 [details]
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
Awesome! Have you tested the library on any of these platforms? The google bug just mentions building.
(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 :-)
Sounds good to me.
Scratch build in rawhide succeeded:
Pushing to branches that have 2.5.0 now.
F20 (rawhide) build:
protobuf-2.5.0-3.fc19 has been submitted as an update for Fedora 19.
* 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).
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.