libunistring version detection w/ "configure -C"

libunistring version detection w/ "configure -C"

[Thien-Thi Nguyen]

[-- Attachment #1: Type: text/plain, Size: 548 bytes --]


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.

-- 
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)               ; (2021) Software Libero
   (pcase (context query)               ;       = Dissenso Etico
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 219 bytes --]

Re: libunistring version detection w/ "configure -C"

[Bruno Haible]

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