On Tue, Feb 16, 2021 at 02:48:03PM -0800, Per Bothner wrote:
> On 2/16/21 2:39 PM, Gavin Smith wrote:
> > It's the C version of the Texinfo::Parser module. I will look at the
> > warnings (I think most of them were due to ignoring the return
> > value of asprintf).
>
> I see a lot of warnings - s
On 2/16/21 2:39 PM, Gavin Smith wrote:
It's the C version of the Texinfo::Parser module. I will look at the
warnings (I think most of them were due to ignoring the return
value of asprintf).
I see a lot of warnings - see attachment (edited down compile log).
Most but not all from parsetexi.
I
On Tue, Feb 16, 2021 at 02:18:45PM -0800, Per Bothner wrote:
> What is parsetexi used for? Doing a 'make' emits a
> lot of compiler warnings in parsetexi.
> If it is experimental or no longer used, perhaps
> it should not be built by default - i.e. it should
> only be built if --enable-parsetexi i
On Tue, Feb 16, 2021 at 02:18:45PM -0800, Per Bothner wrote:
> What is parsetexi used for? Doing a 'make' emits a
> lot of compiler warnings in parsetexi.
> If it is experimental or no longer used, perhaps
> it should not be built by default - i.e. it should
> only be built if --enable-parsetexi i
What is parsetexi used for? Doing a 'make' emits a
lot of compiler warnings in parsetexi.
If it is experimental or no longer used, perhaps
it should not be built by default - i.e. it should
only be built if --enable-parsetexi is specified to configure.
If it is something that should be built by d
