On Thu, Apr 6, 2017 at 4:18 AM, Eryu Guan <eguan@xxxxxxxxxx> wrote: > > On Tue, Apr 04, 2017 at 10:37:22AM -0700, Gwendal Grignou wrote: > > - 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. > > > > Signed-off-by: Gwendal Grignou <gwendal@xxxxxxxxxxxx> > > --- > > > > Changes in v2: > > Removal of instal-sh, use of autoreconf > > > > Changes in v3: > > Use of @exec_prefix@ variable, unify installation location. > > > > Sorry, I didn't notice this in last review. But I don't know why this > AC_CONFIG_MACRO_DIR doesn't work on my RHEL6.9 system (it does work on > RHEL7), make reports: > > configure.ac:5: error: possibly undefined macro: AC_PACKAGE_GLOBALS > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure.ac:6: error: possibly undefined macro: AC_PACKAGE_UTILITIES Checking stack overflow (http://stackoverflow.com/questions/8811381/possibly-undefined-macro-ac-msg-error/8946674), is pkg_config installed on your RH6.9 system. > > ... > > Restoring all the "m4_include" in acinclude.m4 works for me. Just my > data point, not sure what's the proper fix. > > Thanks, > Eryu -- 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
