On Fri, Nov 19, 2021 at 06:12:41PM +0100, Bastian Germann wrote: > xfsprogs fails to cross build from source, because it attempts to build > its crc32 test with the build architecture compiler and thus fails > finding the liburcu, which is only requested for the host architecture. > While this test is useful for native builds, it is not that useful for > cross builds. Skip it by pre-creating the output file. I don't get it. The crcselftest does not use liburcu in any way, nor does it try to link against liburcu, so it should not fail because other parts of xfsprogs use liburcu. What's the build error that occurs? > Reported-by: Helmut Grohne <helmut@xxxxxxxxxx> > Signed-off-by: Bastian Germann <bage@xxxxxxxxxx> > --- > debian/rules | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/debian/rules b/debian/rules > index 6d5b82a8..28cc414d 100755 > --- a/debian/rules > +++ b/debian/rules > @@ -40,6 +40,9 @@ build-arch: built > build-indep: built > built: dibuild config > @echo "== dpkg-buildpackage: build" 1>&2 > +ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH)) > + touch --date=+3day libfrog/crc32selftest > +endif > $(MAKE) $(PMAKEFLAGS) default > touch built We need to fix the generic cross-build problem in the xfsprogs code, not slap a distro-specific build band-aid over it. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
