Update: my libunistring was indeed installed incompletely. A fresh install both implements uc_width and has a header file indicating where to find it. However, correcting that has not helped.
I next sought to identify where the basic system library paths are passed in to $(CC), to see if perhaps they weren't. Unfortunately, in analyzing the Makefiles (post-configuration, obviously, as they don't exist before that), I am stymied by the frequent inclusion of “$(INCLUDES)”. According to grep, this variable is not defined anywhere in the tarball; and it is not listed in the Make manual as being one of the special things that just happen on their own. Where is it being set? > On Aug 14, 2024, at 9:01 AM, bug-wget-requ...@gnu.org wrote: > > Send Bug-wget mailing list submissions to > bug-wget@gnu.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.gnu.org/mailman/listinfo/bug-wget > or, via email, send a message with subject or body 'help' to > bug-wget-requ...@gnu.org > > You can reach the person managing the list at > bug-wget-ow...@gnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Bug-wget digest..." > > > Today's Topics: > > 1. ./configure gets it wrong when libunistring version is > exactly 1.2.0 (Gordon Steemson) > 2. re: ./configure gets it wrong if libunistring version is > exactly 1.2.0 (Gordon Steemson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 13 Aug 2024 16:00:46 -0700 > From: Gordon Steemson <gstee...@gmail.com> > To: bug-wget@gnu.org > Subject: ./configure gets it wrong when libunistring version is > exactly 1.2.0 > Message-ID: <69f2f367-531a-4dc0-8bb4-4a1016767...@gmail.com> > Content-Type: text/plain; charset=us-ascii > > I am attempting to build wget 1.24.5 from the source tarball, and discovered > that `make test` fails to build. A very long investigation revealed that a > needed function, uc_width, is not getting compiled into gnulib: it is > defined in `lib/uniwidth/width.c`, which theoretically gets compiled into > `libgnu-wcwidth.o`, but that never happens because my libunistring's version > (1.2.0) triggers the configure script to comment that build instruction out > of the Makefile (see the areas around line 62720 in `./configure` and around > line 390 in `./lib/Makefile`). I am assuming this to be done by some obscure > M4 macro (perhaps one that came with Gnulib?), because libunistring is not > referenced at all in `configure.ac`. > > I'm going to work around it by either editing the Makefile or installing a > newer version of libunistring, but this seemed like something you ought to be > told about. > > Gordon Steemson > > > ------------------------------ > > Message: 2 > Date: Tue, 13 Aug 2024 16:10:32 -0700 > From: Gordon Steemson <gstee...@gmail.com> > To: bug-wget@gnu.org > Subject: re: ./configure gets it wrong if libunistring version is > exactly 1.2.0 > Message-ID: <9cc97705-9bf9-4033-aea6-57e74e098...@gmail.com> > Content-Type: text/plain; charset=us-ascii > > Update: Libunistring doesn't come any newer than 1.2.0. I don't know if > libunistring built incorrectly on my machine or what, but uc_width is not > present in my copy of it. Is it supposed to be? Where would I even look to > learn that? > > G.S. > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Bug-wget mailing list > Bug-wget@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-wget > > > ------------------------------ > > End of Bug-wget Digest, Vol 190, Issue 2 > ****************************************
