Re: Bootstrap fail, but non-useful message :/

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



(resending, missed including the list first time.  Also reworded some bits)

On 30/11/2010, at 10:51 AM, Eric Blake wrote:
> On 11/29/2010 06:23 AM, Justin Clift wrote
>> configure.ac:13: warning: macro `AM_SILENT_RULES' not found in library
> 
> Warning, but harmless.  We might be able to silence it by doing:
> 
> m4_apply([AM][_SILENT_RULES], [[yes]])
> 
> in configure.ac instead of our direct call to
> 
> AM_SILENT_RULES([yes])

Sounds like it would be a harmless thing to add, so yeah, we should probably
give that a shot.


>> ./bootstrap: autoconf --force ...
>> configure.ac:60: error: possibly undefined macro: AC_MSG_ERROR
>>     If this token and others are legitimate, please use m4_pattern_allow.
>>     See the Autoconf documentation.
> 
> Hmm.  This error seems independent of whether pkg-config is correctly
> installed - it is complaining about a missing autoconf macro.  What
> version of automake and autoconf are installed to begin with?  Bootstrap
> documents that we require 2.59, and 2.59 does provide AC_MSG_ERROR, so I
> can't figure out how it isn't getting expanded.  But bootstrap shouldn't
> have let you get this far if autoconf was older than 2.59.  About the
> only other thing I can think to do is add AC_PREREQ([2.59]) near the
> beginning of configure.ac to give up early if autoconf is too old but
> got past the bootstrap check anyway.  But if your autoconf version
> really is too old, it would be better to patch bootstrap to get the
> version check right.

Just uninstalled the MacPorts version of autoconf, automake, and m4.

These are the system provided versions:

 $ which autoconf
 /usr/bin/autoconf
 $ /usr/bin/autoconf --version
 autoconf (GNU Autoconf) 2.61
 Copyright (C) 2006 Free Software Foundation, Inc.
 This is free software.  You may redistribute copies of it under the terms of
 the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
 There is NO WARRANTY, to the extent permitted by law.

 Written by David J. MacKenzie and Akim Demaille.

 $ which automake
 /usr/bin/automake
 $ /usr/bin/automake --version
 automake (GNU automake) 1.10
 Written by Tom Tromey <tromey@xxxxxxxxxx>
        and Alexandre Duret-Lutz <adl@xxxxxxx>.

 Copyright 2006 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

 $ which m4
 /usr/bin/m4
 $ /usr/bin/m4 --version
 GNU M4 1.4.6
 Copyright (C) 2006 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

 Written by Rene' Seindal.


>> configure.ac:512: error: possibly undefined macro: AC_MSG_NOTICE
> 
> Same category as AC_MSG_ERROR.
> 
>> configure.ac:627: error: possibly undefined macro: PKG_CHECK_MODULES
> 
> Yep, back to the analysis of not finding pkg-config .m4 files.  Maybe
> it's a matter of aclocal not looking in the correct directories for
> installed .m4 files?

Aha, interesting.  It looks like pkg-config wasn't installed on the system when I first ran
that command.  (this gave the reported error)

Though, after installing pkg-config though MacPorts (version 0.25), exact same problem
and error.

After installing the MacPorts version of m4 (1.4.15) again, noticed it's named "gm4", rather 
than "m4".  Wonder if that has any bearing on things?

As I know that installing the MacPorts version of autoconf, automake, and pkg-config together
allow it to work, I've looked if there's a clear "break point" on the way from broken to working:

1) Installing autoconf (2.68) when m4 and pkg-config are already installed, also installs:
  + p5-locale-gettext (1.05-3)
  + help2man (1.38.2)

  Autogen.sh still barfs in the same spot, but a bunch of other output messages before it now,
  seeming to be libtool related.

  There are two system provided libtools.  The OSX /usr/bin/libtool, and the GNU
   /usr/bin/glibtool (2.2.4).

2) Installed automake (1.11.1), and that allowed ./autogen.sh to run.  (barfs later on due to
   missing GnuTLS, but easily fixable).  Didn't need to also install the MacPorts libtool.

Really looks like the MacPort install of automake is needed, and probably autoconf.  But,
it might not be the version causing breakage, rather than macros or something not being
available otherwise.  Wonder how easy it would be to identify the needed one(s), and then
add an explicit test to autogen.sh or the bootstrap?

+ Justin

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]