Opened 8 months ago

Last modified 8 months ago

#18587 new enhancement

Drop usage of old(er) texinfo packages for Haiku's builds

Reported by: bipolar Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Build System Version: R1/beta4
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

Searching for texinfo on Haiku's code base shows that except for x86_64 (that uses texinfo-7.x.x), the rest of the platforms are stuck with older versions (6.1 and even 4.13).

Moving to texinfo-7.x.x (that do not require a version of perl compiled with GCC2) would help solve some issues over HaikuPorts in a manner that requires less gymnastics than trying to accommodate GCC2 and GCC13 perl on x86_32 bits.

Change History (4)

comment:1 by bipolar, 8 months ago

For references:

This says makeinfo, from the textinfo package, is needed to build GCC4.

And seems that in the past, there were some breakages due to texinfo-5, but those got resolved: #9482 and #9483.

Last edited 8 months ago by bipolar (previous) (diff)

comment:2 by waddlesplash, 8 months ago

Component: - GeneralBuild System

comment:3 by begasus, 8 months ago

Grabbed gcc2 sources with haikuporter to do a quick check with makeinfo and the html files for gcc/cpp and iostream. gcc2 and iostream html pages wont build with newer texinto (makeinfo), however I could build the html pages (single page for each though) with the texi2html 1.82 package (this was done on a 64bit machine).

comment:4 by pulkomandy, 8 months ago

I don't know if we build the gcc2 documentation at all anymore?

Back in SVN days we used to play some tricks with file commit dates to make the build think the already generated docs, stored in the SVN, were newer than their sourcefiles. I think now we use Git, it doesn't preserve the file dates, and so we do something similar using "touch".

Maybe there is some simpler option of passing some flag to the configure script to disable documentation generation. Then we wouldn't need texinfo at all.

Or, we could fix the gcc2 docs to build with an up to date version of the tools.

Note: See TracTickets for help on using tickets.