[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-libunistring] Automake 1.16.4 issue
From: |
Bruno Haible |
Subject: |
Re: [bug-libunistring] Automake 1.16.4 issue |
Date: |
Tue, 24 Aug 2021 00:09:23 +0200 |
Hi Jörg,
Following up on our mail exchange from last week:
> > A first patch is attached.
>
> Thanks. Your patch looks interesting. I will see whether I can use it to
> simplify gl_INIT_PACKAGE.
Actually, your patch (0010-AC_INIT.patch) causes a bug that is visible
e.g. in https://packages.debian.org/sid/libunistring-dev :
In the generated binaries, the file /usr/include/unistring/version.h
contains
#define _LIBUNISTRING_VERSION 0x000000
I can reproduce this also in a local build.
You can see the difference in config.status already: It contains
S["HEXVERSION"]="0x000000"
S["VERSION"]=""
where in fact it should contain
S["HEXVERSION"]="0x00090A"
S["VERSION"]="0.9.10"
This, in turn, makes all programs that use the libunistring.m4 macro think
that the installed version is too old:
checking how to link with libunistring... -lunistring
checking for libunistring version... 0.0.0
error: PACKAGE requires libunistring >= 0.9.1.1
Suggestion: Discard your patch and use the one from
https://git.savannah.gnu.org/gitweb/?p=libunistring.git;a=commitdiff;h=15e4365267e316f15222b8bf9f0a7cd0db231e9c
Bruno