Re: Possible bug in configure script
On 1/25/21 1:25 PM, Peter Dyballa wrote: The configure script of wget 1.21.1 seems to have a bug, which becomes visible at least on old Mac OS X versions which use old GCC 4.2, see this report:https://trac.macports.org/ticket/62134. It's my assumption that the tests for C99 and C11 capabilities are incorrect while the maintainer assumes that it's a bug in gnulib I should report. Could you check whether we are both wrong? Or right? The topic has come up before: https://lists.gnu.org/archive/html/bug-gnulib/2021-01/msg8.html but as far as I know nobody has tracked down what's causing the bug. I just now looked at the wget 1.21.1 tarball and it doesn't seem to contain anything Gnulib-relevant. In particular it does not contain a copy of gnulib/m4/std-gnu11.m4. So I don't see why the problem would be due to a bug in Gnulib. wget 1.21.1 was built with Autoconf 2.70, so the following post-2.70 patches to Autoconf might be relevant: https://git.savannah.gnu.org/cgit/autoconf.git/commit/?h=branch-2.70=efc940dc82763b7b2d6e65f04d15d5972d829c0a https://git.savannah.gnu.org/cgit/autoconf.git/commit/?h=branch-2.70=fac6e5e5cf5b974dda2b82d6331d9dcb4b3e0016
Re: Wget 1.21 and PowerMac results
On 1/1/21 10:40 AM, Jeffrey Walton wrote: tempname.c: In function 'random_bits': tempname.c:90: warning: integer constant is too large for 'long' type tempname.c:90: warning: this decimal constant is unsigned only in ISO C90 tempname.c: In function 'try_tempname_len': tempname.c:288: error: 'for' loop initial declaration used outside C99 mode Presumably your compiler has a flag to enable C99-or-better mode. If not, you're out of luck: Gnulib assumes C99 nowadays. If so, please investigate why 'configure' did not set that flag. With ancient GCC, 'configure' should try the -std=gnu99 option; why didn't that work for you? Please check your config.log to find out.
Re: [Bug-wget] wget fails to build under HP-UX 11.00
On 08/19/2011 06:23 AM, Giuseppe Scrivano wrote: it seems related to gnulib What makes you think that? The error came when compiling gnulib source code, true, but the diagnostic makes it look like there's an '#include ./' in config.h, or something like that, which could well be non-gnulib related.