On Thu, Jan 26, 2017 at 5:45 PM, Theodore Ts'o wrote: > On Mon, Jan 23, 2017 at 09:57:15AM -0800, Gwendal Grignou wrote: >> https://chromium-review.googlesource.com/#/c/424191 >> - Chromeos needs libtool to (cross-)compile packages and put them at >> the right place. I needed to move archived aclocal.m4 to acinclude.m4. >> Does it make sense to require aclocal to run to compile xfstests? > > I'm kind of curious why you need libtool to be able to cross-compile > packages. > > I've been cross-compiling xfstests to armhf, ppcle, and arm64 without > any issues. > > See: https://git.kernel.org/cgit/fs/ext2/xfstests-bld.git/tree/build-all > > Are you trying to build with shared libraries, or some such? it isn't about "needing" libtool, nor what we're attempting to do. we don't care if xfstools uses libtool or plain automake rules or something else. however, xfstests itself already utilizes `libtool` to compile+link things, and indeed to also create libs like libtest.la and libdmtest.la. the host `libtool` is specifically generated with settings that target the host system only. just grep for your tuple in there (e.g. `grep x86_64 /usr/bin/libtool`) to see. for simpler builds, the differences might go unnoticed as a happy accident. by using LT_INIT in autoconf, it'll include a libtool script that configure will create & use automatically tailored for the current target. -mike -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
