Re: ambiguous @*table with argument missing formatter argument message

2022-12-08 Thread Raymond Toy
On Thu, Dec 8, 2022 at 2:59 PM Patrice Dumas wrote: > Hello, > > Not sure about that as I am not a native english speaker. When a > @*table does not have an @-command formatter for the items, the error > message is > > d.texi:2: table requires an argument: the formatter for @item > > This messag

ambiguous @*table with argument missing formatter argument message

2022-12-08 Thread Patrice Dumas
Hello, Not sure about that as I am not a native english speaker. When a @*table does not have an @-command formatter for the items, the error message is d.texi:2: table requires an argument: the formatter for @item This message seems fine to me if there is no argument for @*table, however, if t

Re: namespacing issues with Gnulib

2022-12-08 Thread Paul Eggert
On 2022-12-08 12:19, Arsen Arsenović wrote: The one that pops to mind is prefixing everything with ``gl_'', and exposing aliases maybe. The former is unergonomic and latter is fragile, though. Yes, my take on this is to leave Gnulib alone, and change the app to not attempt to redefine Gnulib'

Re: -Wlto-type-mismatch warning in error()

2022-12-08 Thread Arsen Arsenović
Hi, Eli Zaretskii writes: >> On top of that, Gnulib is pulling in error anyway: >> >> $ nm ./gnulib/lib/libgnu.a | grep error >> U error >> $ nm install-info.o ../gnulib/lib/libgnu.a |& grep '\' >> T error >> U error > > Not sure what you wanted to demonstrate

Re: namespacing issues with Gnulib

2022-12-08 Thread Arsen Arsenović
Bruno Haible writes: > Any other ideas? The one that pops to mind is prefixing everything with ``gl_'', and exposing aliases maybe. The former is unergonomic and latter is fragile, though. -- Arsen Arsenović signature.asc Description: PGP signature

Re: namespacing issues with Gnulib

2022-12-08 Thread Eli Zaretskii
> From: Bruno Haible > Cc: gavinsmith0...@gmail.com, s...@gentoo.org, bug-texinfo@gnu.org, > bug-gnu...@gnu.org > Date: Thu, 08 Dec 2022 20:00:31 +0100 > > Eli Zaretskii wrote: > > > Attempting to --whole-archive link on that platform grants us: > > > > > > $ x86_64-linux-musl-gcc -o ginstall-i

Re: namespacing issues with Gnulib

2022-12-08 Thread Bruno Haible
Eli Zaretskii wrote: > > Attempting to --whole-archive link on that platform grants us: > > > > $ x86_64-linux-musl-gcc -o ginstall-info install-info.o \ > > -Wl,--whole-archive ../gnulib/lib/libgnu.a -Wl,--no-whole-archive > > /usr/libexec/gcc/x86_64-linux-musl/ld: > > ../gnulib/lib/libgnu.a(l

Re: -Wlto-type-mismatch warning in error()

2022-12-08 Thread Eli Zaretskii
> From: Arsen Arsenović > Cc: Bruno Haible , gavinsmith0...@gmail.com, > s...@gentoo.org, bug-texinfo@gnu.org, bug-gnu...@gnu.org > Date: Thu, 08 Dec 2022 09:25:01 +0100 > > > Shouldn't we report this to the GCC folks? It could be a bug in lto, > > no? I mean, 'error' is not a symbol that appl

Re: -Wlto-type-mismatch warning in error()

2022-12-08 Thread Arsen Arsenović via Bug reports for the GNU Texinfo documentation system
Hi, Eli Zaretskii writes: >> Whereas with the Gnulib 'error' module, there is a conflict between the >> two global function definitions (with 'T' linkage) in install-info.c and >> in error.c *always*. >> >> > The simplest way to fix this problem would probably be to rename the >> > "error" >>