On Mon, Aug 06, 2012 at 06:59:37PM -0400, George Spelvin wrote: > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > debuild: fatal error at line 1350: > dpkg-buildpackage -rfakeroot -d -us -uc -b -ai386 failed I don't think -ai386 will work for e2fsprogs since we need external libraries; specifically, libblkid-dev and libuuid-dev and the dev packages aren't multiarch compatible. (In fact, I'm not sure -ai386 to build 32-bit packages in an x86 environment will work in general. It's certainly not the standard way 32-bit packages are built.) The failures you're seeing is because "pkg-config --libs blkid" is returning a null string when run in the dpkg-buildpackage -ai386 environment --- which is not surprising, since we don't have a -32/-64 bit link libraries in libblkid-dev. So if you want to build a 32-bit set of packages of e2fsprogs, you'll need to make a 32-bit build environment as a chroot, using debootstrap and build e2fsprogs in the 32-bit chroot. That's actually how I build my packages for Debian, BTW --- I have a 32-bit chroot, and I build the binary packages for i386 and upload them from there. I let the autobuilders build the 64-bit binary packages from the source upload. That way, the most commonly used binary packages are built in a standard autobuilder environment, and are not subject to the vagracies of my build environment. It also means that I don't have to worry about the build scripts bitrot for the 32-bit packages. (I also build 64-bit debs for my own use --- but I don't upload them.) Regards, - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
