Re: [libvirt] Bootstrap fail, but non-useful message :/
On 30/11/2010, at 1:26 AM, Jim Meyering wrote:
Justin Clift wrote:
> On 30/11/2010, at 12:35 AM, Matthias Bolte wrote:
>> Looks like the system is missing pkg-config, or at least has the .m4
>> file is in an unexpected place so that autoconf can't find it.
>>
>> bootstrap checks for pkg-config, so the binary is probably there, but
>> that doesn't mean that autoconf can find the corresponding .m4 file,
>> if it's there at all.
>
> Interesting. When installing autoconf, MacPorts also installs a newer m4
> than the system provided one too.
>
> I wonder if there's a better way to cope with this m4 related failure scenario,
> than the text presently being given?
I'm sure there is, but is it worth it?
Yep, good point. If the solution is easy, that would be nifty.
In practical terms, it just means a MacPort for libvirt will have the MacPort
autoconf and automake as dependencies. All pretty easy (when I get around
to that).
If lots of developers hit this, then maybe...
For now, your best bet might be to build the latest versions
of those tools yourself, e.g., via this script:
http://people.redhat.com/meyering/autotools-install
Once you've downloaded it, run
bash autotools-install --help
Thanks Jim. :)