Re: fatal: ambiguous message

[Eric Blake]

On 12/30/2010 06:37 PM, Bruce Korb wrote:
> Hi,
> 
> Is this fatal?  If so, how come it continued?

It's fatal to git-version-gen, which did not continue.  However, the
rest of autoconf failed to check m4_sysval to see if the m4_esyscmd had
non-zero status, so that's why autoconf continued.

> If not, then why does it say, "fatal"?
> What is really wrong?  This looks like it is trying to extract
> a git version and fiddle something, but is not doing it correctly.

git-version-gen should be patched to include $0 in fatal error messages,
to make the message more clear.  Meanwhile, you should trace
git-version-gen to see why it cannot determine the proper git version
string to use based on your setup.

> 
> the configure.ac file starts with this:
> 
>> AC_INIT([GNU libposix],
>>     m4_esyscmd([./git-version-gen .tarball-version]),
>>     address@hidden)

Also, you should patch configure.ac to add an additional line:

m4_if(m4_sysval, [0], [],
 [m4_fatal([git-version-gen failed, please investigate])])

after the AC_INIT, so that autoconf won't disregard fatal errors in
git-version-gen.

-- 
Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

signature.asc
Description: OpenPGP digital signature