On 12/30/19 4:09 AM, Milan Kupcevic wrote:
> I've seen BeagleBone Black and Raspberry Pi mini cluster setups used in > classroom environment for educational purposes. We should provide them, > if possible. > > As for failing builds on arm architectures it probably does not make > sense to push for ARM NEON on armel as it targets hardware with no float > acceleration. Debian's target on armel is --with-arch=armv5te > --with-float=soft. Even if we'd patch the build process to detect armel properly, I'd assume it would fail with the same issue as armhf - see below. > On the other hand the armhf arch on Debian is specifically targeting > hardware with float acceleration. Default target is --with-arch=armv7-a > --with-fpu=vfpv3-d16 --with-float=hard. NEON is more likely to be > available on this one. > > NEON is safely available on arm64, aarch64-linux-gnu > > See https://en.wikipedia.org/wiki/ARM_architecture#Advanced_SIMD_(NEON) > for more info. yes, armhf builds much further with clang than with gcc and does not complain about NEON, but it fails with [ 60%] Building CXX object src/rgw/CMakeFiles/rgw_common.dir/services/svc_zone.cc.o cd /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/src/rgw && /usr/bin/clang++ -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D__linux__ -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/src/include -I/<<PKGBUILDDIR>>/src -I/usr/include/nss -I/usr/include/nspr -I/<<PKGBUILDDIR>>/src/dmclock/support/src -isystem /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/include -isystem /<<PKGBUILDDIR>>/src/xxHash -isystem /<<PKGBUILDDIR>>/src/rapidjson/include -isystem /<<PKGBUILDDIR>>/src/rgw/services -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wtype-limits -Wignored-qualifiers -Winit-self -Wpointer-arith -Werror=format-security -fno-strict-aliasing -fsigned-char -Wno-unknown-pragmas -Wno-unused-function -Wno-unused-local-typedef -Wno-varargs -Wno-gnu-designator -Wno-missing-braces -Wno-parentheses -Wno-deprecated-register -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -ftemplate-depth-1024 -Wnon-virtual-dtor -Wno-unknown-pragmas -Wno-ignored-qualifiers -Wno-inconsistent-missing-override -Wno-mismatched-tags -Wno-unused-private-field -Wno-address-of-packed-member -fdiagnostics-color=auto -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free -fPIC -DHAVE_CONFIG_H -D__CEPH__ -D_REENTRANT -D_THREAD_SAFE -D__STDC_FORMAT_MACROS -std=c++17 -o CMakeFiles/rgw_common.dir/services/svc_zone.cc.o -c /<<PKGBUILDDIR>>/src/rgw/services/svc_zone.cc In file included from /<<PKGBUILDDIR>>/src/rgw/services/svc_zone.cc:7: /<<PKGBUILDDIR>>/src/rgw/rgw_rest_conn.h:441:28: error: template parameter redefines default argument template <class T, class E=int> ^ /<<PKGBUILDDIR>>/src/rgw/rgw_rest_conn.h:437:32: note: previous default template argument defined here template <class T, class E = int> ^ Which is clearly not valid in c++, but gcc accepts it. Also I'm not motivated to create patches to make ceph build with clang and maintain them... So I think for now mipsel, armel and armhf have to go. I've opened a bug against gcc: #947751 So if nobody is going to stop me, I'll remove mipsel, armel and armhf for now. Bernd -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
