Control: tags -1 + help On Fri, Jan 04, 2019 at 02:47:07PM +0000, Steve McIntyre wrote: > Package: src:criu > Version: 3.8.1-1 > Severity: important > > Hi! > > I've been doing a full rebuild of the Debian archive, building all > source packages targeting armel and armhf using arm64 hardware. We are > planning in future to move all of our 32-bit armel/armhf builds to > using arm64 machines, so this rebuild is to identify packages that > might have problems with this configuration. > > I've tried to build criu for armhf on top of arm64, and it's failing > to build: > > ... > PBCC images/pipe-data.pb-c.c > PBCC images/sk-packet.pb-c.c > PBCC images/pstree.pb-c.c > PBCC images/fs.pb-c.c > In file included from include/common/lock.h:9, > from compel/plugins/std/infect.c:5: > include/common/asm/atomic.h:61:2: error: #error ARM architecture version > (CONFIG_ARMV*) not set or unsupported. > #error ARM architecture version (CONFIG_ARMV*) not set or unsupported. > ^~~~~ > include/common/asm/atomic.h: In function 'atomic_add_return': > include/common/asm/atomic.h:82:2: error: implicit declaration of function > 'smp_mb' [-Werror=implicit-function-declaration] > smp_mb(); > ^~~~~~ > PBCC images/eventpoll.pb-c.c > AR soccr/libsoccr.a > PBCC images/eventfd.pb-c.c > cc1: all warnings being treated as errors > make[2]: *** > [/home/steve/debian/build/criu/criu-3.8.1/scripts/nmk/scripts/build.mk:208: > compel/plugins/std/infect.o] Error 1 > make[1]: *** [Makefile.compel:52: compel/plugins/std.lib.a] Error 2 > make[1]: *** Waiting for unfinished jobs.... > ... > > It's blindly using the output of uname and assuming that's the right > answer for the target system. I *might* be building on a system that's > showing as "armv8l", but I'm building *for* armhf which is ARMv7 not > ARMv7. This package could do with a way to specify what the target is > via configuration, rather than the simple parsing of uname that's > currently hard-coded in the Makefile.
I still can confirm this up to the current version. In case you have a good idea how to less invasive as possible this can be handled that would defintively be welcome. Regards, Salvatore
