tag 556944 + confirmed pending thanks Hi Riku,
I will simply make zfs-fuse Arch:any, and wait for the corresponding FTBFS, if any. The current arch limitations have apparently been fixed a while ago. Cheers, --Seb On Nov/18, Riku Voipio wrote: > Package: zfs-fuse > Version: 0.6.0~beta+433snapshot-1 > Severity: normal > User: debian-...@lists.debian.org > Usertag: eabi > > Please make zfs-fuse more portable. At least specify what is > needed (big/little-endian, pointer size, foo?) rather than > blindly blacklist all unknown arches. > > > dpkg-buildpackage: set CXXFLAGS to default value: -g -O2 > > dpkg-buildpackage: source package zfs-fuse > > dpkg-buildpackage: source version 0.6.0~beta+433snapshot-1 > > dpkg-buildpackage: host architecture armel > > /usr/bin/fakeroot debian/rules clean > > dh_testdir > > dh_testroot > > rm -f build-stamp configure-stamp > > # Add here commands to clean up after the build process. > > scons -c -C src > > scons: Reading SConscript files ... > > > > Sorry, only the x86, amd64 and sparc64 hardware architectures are supported > > make: *** [clean] Error 1 > > dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules clean gave error > > exit status 2 > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
