Am 05.03.2014 01:01, schrieb Diane Holt: > Is that supposed to be possible? When I add --disable-multilib to the > configure options, the build fails on the install, because it hasn't built > any of src/gcc-linaro-4.8-2014.02/libgcc: > > /bin/sh ../../../../src/gcc-linaro-4.8-2014.02/libgcc/../mkinstalldirs > /home/ubuntu/work483/build/sysroot/home/ubuntu/opt/cross-gcc-linaro/lib/gcc/arm-linux-gnueabi/4.8.3 > /usr/bin/install -c -m 644 libgcc_eh.a > /home/ubuntu/work483/build/sysroot/home/ubuntu/opt/cross-gcc-linaro/lib/gcc/arm-linux-gnueabi/4.8.3/ > /usr/bin/install: cannot stat `libgcc_eh.a': No such file or directory > make[3]: *** [install-shared] Error 1 > make[3]: Leaving directory > `/home/ubuntu/work483/build/gcc/arm-linux-gnueabi/libgcc' > make[2]: *** [install-target-libgcc] Error 2 > make[2]: Leaving directory `/home/ubuntu/work483/build/gcc' > make[1]: *** [install] Error 2 > make[1]: Leaving directory `/home/ubuntu/work483/build/gcc' > make: *** [stamp/gcc-install] Error 2 > > I don't want or need multilib, so I'd rather build the toolchain without > it, but before I try to make that happen, I wanted to make sure it's > supposed to be able to get built correctly that way.
yes, I had to revert that Linaro local patch as well (not to disable building multilibs, but to be able to build the Ubuntu multilibs (soft-float/hard-float). Matthias 2014-01-16 Zhenqiang Chen <zhenqiang.c...@linaro.org> Linaro local patch for armv4t multilib support. * gcc/config/arm/t-mlibs: New file. * config.gcc: Add t-mlibs. * incpath.c (add_standard_paths): Try multilib path first. * gcc.c (for_each_path): Likewise. _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain