Follow-up Comment #11, bug #50223 (project wget):
The commit to add wcwidth to bootstrap.conf did not help me, but upon further
investigation, I realized that it was because I have libunistring installed
(which, if linked, provides uc_width); if I move libunistring out of the way,
I have no problem with compilation. Therefore, this may not be a problem for
most users.
That said, the libunistring problem is a weird one. configure does check for
libunistring:
./configure | grep libunistring
checking whether included libunistring is requested... no
checking for libunistring... yes
checking how to link with libunistring... -L/usr/local/lib -lunistring
checking for libunistring version... 0.9.7
checking whether to use the included libunistring... no
but it doesn't set the proper ld flags:
$ grep LIBUNISTRING= config.log
HAVE_LIBUNISTRING='yes'
LIBUNISTRING=''
LTLIBUNISTRING=''
(the above should instead be:
$ grep LIBUNISTRING= config.log
HAVE_LIBUNISTRING='yes'
LIBUNISTRING='-L/usr/local/lib -lunistring'
LTLIBUNISTRING='-L/usr/local/lib -lunistring -R/usr/local/lib'
)
Interestingly, I created a dummy project where I ran
gnulib/gnulib-tool --import libunistring-optional
then with boilerplate configure.ac and automake.am, the generated configure
would set LIBUNISTRING and LTLIBUNISTRING to the correct values. Not sure
where the problem is.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50223>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
