Bug 663426

Summary:	dev-build/autoconf-2.69-r4: old hack fails with a longer slot number
Product:	Gentoo Linux	Reporter:	Nikita Zlobin <cook60020tmp>
Component:	Current packages	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED FIXED
Severity:	normal	CC:	arsen, jstein
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=902461
Whiteboard:
Package list:		Runtime testing required:	---

Description Nikita Zlobin 2018-08-12 08:31:15 UTC

I have installed autoconf-2.69 and 2.13 versions, all include own book versions.
Book version from 2.69 includes section "Portable C and C++", right after "Portable Make" and before "Manual Configuration". All sections, begining with "Portable C and C++" are unavailable for info reader from texinfo, which gives error: "No such file or directory". It is impossible even to get past this margin via search. E.g., if i search for AC_ARG_ENABLE (trying get to Site Configuration), it says "Cannot find node '(autoconf-2)VPATH and Make".

However, in info autoconf-2.1 there is no problems entering "Manual Configuration" and further.

But yet, other info readers (tried emacs, pinfo, tkinfo) have no mentioned problem with autoconf-2.69 too - actually i use tkinfo.

I can't understand, whose is that bug: invalid section in autoconf-2.69 book or error in texinfo reader.

Updating texinfo to 6.4 or 6.5 doesn't fix problem.

Though 6.5 item from NEWS mentions:
"another bug which could make nodes inaccessible in long "split" info files"
probably it is not about this bug.

Comment 1 Rafał Mużyło 2019-06-05 16:28:52 UTC

...this is a bit misfiled

The problem has nothing to do with texinfo and just about everything with toolchain-autoconf eclass.

That old hack to prevent dependency loop by using neither makeinfo nor any of autotools, just sed, seems to fail once the slot number is 2.69.

I'm not sure how exactly info viewer works, but after series of test my guess is that after adding that much text to the file, some of the offsets are off by by too much for things to still work.

Unfortunatelly, short of rebuilding the page with makeinfo, I see no simple solution.

Comment 2 Sam James archtester

2024-01-16 07:20:49 UTC

I suspect this was either fixed by the work for bug 902461 or was the same thing.