On Fri, Jan 27, 2017 at 6:37 AM, Theodore Ts'o wrote: > On Thu, Jan 26, 2017 at 10:40:39PM -1000, Mike Frysinger wrote: > > 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. > > Right, but I'm able to create libtool without any problems and messing > with aclocal.m4 and acinclude.m4, et. al. I probably am relying on > libtoolize from the local Debian or Guubuntu build host, though. Is > that the issue you're having with ChromeOS? That you're using a > different version of the libtool/autoconf macros? if we wanted, we could do all this manually too, but i don't think it makes sense to force every developer to learn autotools and how to set up a local copy. Gwendal's patch makes things "just work" w/out having to learn anything new. the overhead is, arguably, negligible. -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
