Opened 17 years ago

Closed 17 years ago

#2074 closed enhancement (fixed)

Texinfo-4.11

Reported by: Matthew Burgess Owned by: lfs-book@…
Priority: normal Milestone: 7.0
Component: Book Version: SVN
Severity: normal Keywords:
Cc:

Description

New version.

I've not tested compilation yet, but there's one known issue which is that `which' is required by the test suite: http://lists.gnu.org/archive/html/bug-texinfo/2007-09/msg00019.html

Also, the current multibyte patch fails to apply, due to changes in info/info.c. Similarly, the current tempfile patch fails to apply, due to changes in util/texindex.c.

Change History (4)

comment:1 by Matthew Burgess, 17 years ago

Tempfile issue has been addressed in a different manner upstream. See http://cvs.savannah.gnu.org/viewvc/texinfo/util/texindex.c?root=texinfo&r1=1.17&r2=1.18 so the current tempfile patch can just be dropped.

comment:2 by Matthew Burgess, 17 years ago

Multibyte patch was applied as-is. See http://cvs.savannah.gnu.org/viewvc/texinfo/info/info.c?root=texinfo&r1=1.13&r2=1.14 and http://cvs.savannah.gnu.org/viewvc/texinfo/info/man.c?root=texinfo&r1=1.6&r2=1.7. A slight change has since been made to conditionalize LC_MESSAGES. Regardless, the current multibyte patch can be dropped too.

comment:3 by Matthew Burgess, 17 years ago

This causes problems for at least Binutils and GCC due to them not catering for 2 digit numbers in their configure checks for texinfo.

There's a patch for binutils at http://sourceware.org/cgi-bin/cvsweb.cgi/src/configure.diff?r1=1.277&r2=1.278&cvsroot=src. It might be nice if we could get that into a sane looking sed. If not, the patch will have to do, I guess.

There are 2 patches for GCC at http://gcc.gnu.org/ml/gcc-patches/2007-09/msg01271.html and http://gcc.gnu.org/ml/gcc-patches/2007-09/msg01729.html. Given that upstream will probably release GCC-4.2.2 real soon now, we may as well leave the Texinfo upgrade until that's out.

comment:4 by Matthew Burgess, 17 years ago

Resolution: fixed
Status: newclosed

Fixed in r8439.

Note: See TracTickets for help on using tickets.