From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ipmail06.adl2.internode.on.net ([150.101.137.129]:2247 "EHLO ipmail06.adl2.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751709AbeEEBgO (ORCPT ); Fri, 4 May 2018 21:36:14 -0400 Date: Sat, 5 May 2018 11:36:12 +1000 From: Dave Chinner Subject: Re: [PATCH] Use the original install-sh file from SGI Message-ID: <20180505013612.GG23861@dastard> References: <20180503050728.25779-1-tytso@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180503050728.25779-1-tytso@mit.edu> Sender: fstests-owner@vger.kernel.org To: Theodore Ts'o Cc: fstests@vger.kernel.org List-ID: On Thu, May 03, 2018 at 01:07:28AM -0400, Theodore Ts'o wrote: > The install-sh file is much more efficient than the libtool version > (50% faster wall clock time; much more than that when running in a > qemu emulation build environment). There doesn't seem to be any real > need for the libtool version, so bring back the original install-sh > script. > > Signed-off-by: Theodore Ts'o > --- > > A very large amount of time when running "make install" in a build > chroot using qemu emulation, such as constructed by running "sudo > setup-buildchroot --arch-armhf" using the script found here[1] is in > running the install-sh provided by libtool, which is amazing bloated > and forks a crazy number of processes to do something very simple. > > As near as I can tell there is zero benefit in using the install-sh > provided by libtool, so restore the version that SGI originally used. > > [1] https://github.com/tytso/xfstests-bld/blob/master/setup-buildchroot Does this break cross-compilation for chromeeOS? I ask, because that is why the hard coded install-sh was originally replaced by the libtool provided one last year: commit 5d20084fefaf09e86be26d7c71bd1c7ac2a2b35c Author: Gwendal Grignou Date: Wed Apr 19 16:33:48 2017 -0700 build: allow cros-compilation on chromeOS - Request LIBTOOL to be used - Set topbuildir based on a Makefile variable to call libtool - Use /usr/local instead of /var for xfstest final location - Move macros from aclocal.m4 to acinclude.m4, aclocal.m4 is autogenerated. - Use autoconf variables @prefix@, @exec_prefix@. The regular way of compiling xfstests - make - remains. But it now runs autoreconf and libtoolize -i to produce a valid configure. Verified with 'make install --dry-run' that files are installed at the same place. Verified compiling in chromeOS chroot works as well. [eguan: resolve merge conflicts and update .gitignore and remove generated files by realclean] Signed-off-by: Gwendal Grignou Reviewed-by: Eryu Guan Signed-off-by: Eryu Guan Cheers, Dave. -- Dave Chinner david@fromorbit.com