[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libunistring version detection w/ "configure -C"
From: |
Bruno Haible |
Subject: |
Re: libunistring version detection w/ "configure -C" |
Date: |
Sun, 25 Jul 2021 15:28:45 +0200 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-210-generic; KDE/5.18.0; x86_64; ; ) |
Thien-Thi Nguyen wrote on 2021-01-26:
> At <https://bugs.gnunet.org/view.php?id=6722>, there is a patch
> to libunistring version detection w/ "configure -C". Does that
> look right? It seems strange to me.
I can not reproduce the problem: Configuring gnunet-0.14.1 with
./configure -C --with-libunistring-prefix=/gnu-inst-libunistring/0.9.10
twice in a row produces the same config.cache in each run, and the
second run succeeds just like the first one.
The patch is also nonsense because it introduces invalid shell
syntax in the configure script: It replaces the valid code
if test ${gl_cv_libunistring_version+y}
then :
with
if { as_var=gl_cv_libunistring_version, gl_libunistring_hexversion; eval test
\${$as_var+y}; }
then :
I hope the author of that patch is not from the University of Minnesota...
Bruno
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: libunistring version detection w/ "configure -C",
Bruno Haible <=