On 2015-10-27, Emilio Pozuelo Monfort wrote: > On 27/10/15 18:20, Vagrant Cascadian wrote: >> On 2015-10-27, Emilio Pozuelo Monfort wrote: >> Unfortunately, the patch FTBFS for me: >> >> arm-linux-gnueabihf-strip --remove-section=.comment >> debian/build/tools/tools/kwboot >> arm-linux-gnueabihf-strip --remove-section=.comment >> debian/build/tools/tools/mksunxiboot >> set -e; for platform in `cat debian/build/rksd`; do \ >> debian/build/tools/tools/mkimage -T rksd -d >> $platform/spl/u-boot-spl-dtb.bin $platform/spl/u-boot-spl-dtb.rksd; \ >> done >> /bin/sh: 2: debian/build/tools/tools/mkimage: not found >> make[1]: *** [override_dh_auto_build] Error 127 >> debian/rules:30: recipe for target 'override_dh_auto_build' failed >> make[1]: Leaving directory '/«BUILDDIR»/u-boot-2015.10+dfsg1' >> make: *** [build] Error 2 > > I guess you're cross-building?
Yes, was cross-building. Spent some effort recently getting cross-building u-boot working again, and would be unfortunate to not be able to anymore... > mkimage was just stripped, so it should exist. It fails to run because > it's an ARM binary but you're on amd64... or so I guess :) > > The "not found" error is just misleading and what happens when you try to run > an > ELF binary from another architecture that your system doesn't support. Sounds plausible. live well, vagrant
signature.asc
Description: PGP signature
