Follow-up Comment #14, bug #50223 (project wget):
$ ls -la m4/libunistring*.m4
-rw-r--r-- 1 tim tim 6320 Feb 4 15:22 m4/libunistring-base.m4
-rw-r--r-- 1 tim tim 6348 Feb 4 15:22 m4/libunistring.m4
-rw-r--r-- 1 tim tim 961 Feb 4 15:22 m4/libunistring-optional.m4
What you could do to debug the emptiness of (LT)LIBUNISTRING:
Edit m4/libunistring.m4, put some 'echo' lines printing $LIBUNISTRING. The
*.m4 files are translated into shell code (the ./configure script). You will
see your echoes in the output of ./configure. That is what I would do (and did
a few times when developing m4 macros).
There are not so many places where (LT)LIBUNISTRING is set:
```
m4/libunistring.m4: HAVE_LIBUNISTRING=no
m4/libunistring.m4: LIBUNISTRING=
m4/libunistring.m4: LTLIBUNISTRING=
m4/libunistring.m4: LIBUNISTRING=
m4/libunistring.m4: LTLIBUNISTRING=
m4/libunistring.m4: LIBUNISTRING="$LIBUNISTRING $LIBICONV"
m4/libunistring.m4: LTLIBUNISTRING="$LTLIBUNISTRING $LTLIBICONV"
```
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50223>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
