tech-toolchain archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
re: further texinfo lossage with GCC 15.1
> What is the best way to deal with this lossage? I figure we're not
> updating texinfo anytime soon because the latest version requires Perl.
>
> 3 options from the top of my head:
>
> 1. we disable the appropriate GCC warning in tools/texinfo/Makfile for all of
> texinfo
> 2. we disable the appropriate GCC warning for cmds.c and makeinfo.c only.
> Not sure where best to do that.
> 3. we hack cmds.[hc] and makeinfo.c so that the problem goes away. I guess
> this mean to change all command functions to take 3 args and mark some of
> them __unused. This is the most work, obviously.
our texinfo is orphaned at this point (last gpl2 version) so i'm more
inclined just to fix this in the sources. ie #3.
i'm not really sure why we turn on -Werror for tools like this, or is
this now *always* an error, previously was a warning? in generally,
we tend to avoid -Werror for tools builds using non-bsd.*.mk framework.
(it's much harder to avoid warnings on older, or newer, or non-netbsd
platforms.)
if it's just removing -Werror from here, that would also be OK.
for #2, the best places to do that is in the sources themselves with
#pragma, etc.
> For 1. and 2. do we need to introduce a correspong CC_WNO_... in bsd.own.mk?
this won't help. those are for building in-tree parts, not tools, and
especially not for autotools style src/tools/ subdirs.
.mrg.
Home |
Main Index |
Thread Index |
Old Index