In file included from /var/tmp/portage/sys-cluster/ceph-12.2.5/work/ceph-12.2.5/src/common/ceph_context.cc:22:0: /var/tmp/portage/sys-cluster/ceph-12.2.5/work/ceph-12.2.5/src/common/ceph_crypto.h:38:23: error: ‘byte’ does not name a type HMACSHA1 (const byte *key, size_t length) ^~~~ /var/tmp/portage/sys-cluster/ceph-12.2.5/work/ceph-12.2.5/src/common/ceph_crypto.h: In constructor ‘ceph::crypto::HMACSHA1::HMACSHA1(const int*, size_t)’: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome-systemd_20180510-100752 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.7.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv sys-cluster/ceph [ebuild N ] sys-cluster/ceph-12.2.5 USE="ldap mgr radosgw ssl systemd tcmalloc -babeltrace -cephfs -fuse -jemalloc -lttng -nss -static-libs (-system-boost) {-test} -xfs -zfs" CPU_FLAGS_X86="sse sse2 sse3 sse4_1 sse4_2 ssse3" PYTHON_TARGETS="python2_7 python3_5 -python3_4 -python3_6"
Created attachment 531068 [details] emerge-info.txt
Created attachment 531070 [details] emerge-history.txt
Created attachment 531072 [details] environment
Created attachment 531074 [details] etc.portage.tbz2
Created attachment 531076 [details] logs.tbz2
Created attachment 531078 [details] sys-cluster:ceph-12.2.5:20180512-162551.log
Created attachment 531080 [details] temp.tbz2
Seems like Downgrading crypto++ to 5.6.5-r1 "fixes" that.
Same issue here. It looks like Ceph supports using NSS for crypto instead of crypto++. I just tried building with +nss -ssl and that works. So the default should probably be to use nss. Looks like the crypto++ dep is being excised from Ceph anyway: https://tracker.ceph.com/projects/ceph/repository/revisions/a18f0589c0641e588f1e09d432fc224fa3fc27aa/diff http://tracker.ceph.com/issues/812 So it probably makes sense to just fix the ebuild to disable crypto++ support, which I'm guessing isn't getting much testing upstream and will probably be gone in future versions.
*** Bug 656154 has been marked as a duplicate of this bug. ***
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=01123bf43f017332690278f44079d572b3fc7935 commit 01123bf43f017332690278f44079d572b3fc7935 Author: Patrick McLean <chutzpah@gentoo.org> AuthorDate: 2018-06-13 17:52:41 +0000 Commit: Patrick McLean <chutzpah@gentoo.org> CommitDate: 2018-06-13 17:52:41 +0000 sys-cluster/ceph: Depend on <crypto++-7 in 12.2.5 Closes: https://bugs.gentoo.org/655588 Package-Manager: Portage-2.3.40, Repoman-2.3.9 sys-cluster/ceph/ceph-12.2.5.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
