Current erlang-eleveldb 2.2 fails to build on all secondary arches due ... + make cc -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -DSNAPPY -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -march=z9-109 -mtune=z10 -fPIC -MM -E -MT port/port_posix.d -MT port/port_posix.o -MF port/port_posix.d port/port_posix.cc In file included from ./port/port_posix.h:45:0, from port/port_posix.cc:5: ./port/atomic_pointer.h:143:2: error: #error Please implement AtomicPointer for this platform. #error Please implement AtomicPointer for this platform. ^~~~~ ... The problem seems to be caused by the bundled leveldb 2.0.19 where it checks for <cstdatomic> in build_detect_platform while recent gcc 5.x or 6.x are providing <atomic>. See eg. https://github.com/google/leveldb/blob/master/build_detect_platform#L180 links to failed builds are eg. http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=2244725 http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=3419255 http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=3573239 Version-Release number of selected component (if applicable): erlang-eleveldb-2.2.19-1.fc25 but seems all version >= 2.2 have the same problem
upstream fix at https://github.com/basho/leveldb/pull/194
erlang-eleveldb-2.2.19-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-20b830da3d
erlang-eleveldb-2.2.19-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-20b830da3d
erlang-eleveldb-2.2.19-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.