build failure on Debiian Jessie, texinfo again.
Heater.
Posts: 21,230
I'm trying to build propgcc (default branch) on Debian Jessie, on a Raspberry Pi as it happens,
binutils fails to build with:
../../../../propgcc/binutils/bfd/doc/bfd.texinfo:325: unknown command `colophon'
../../../../propgcc/binutils/bfd/doc/bfd.texinfo:336: unknown command `cygnus'
Seems to be a problem that is reported the world over.
Not really looking for a fix but does anyone how to build binutils and all without having to generate that texinfo junk? No one uses that stuff and it just wastes space and makes builds fail all the time.
binutils fails to build with:
../../../../propgcc/binutils/bfd/doc/bfd.texinfo:325: unknown command `colophon'
../../../../propgcc/binutils/bfd/doc/bfd.texinfo:336: unknown command `cygnus'
Seems to be a problem that is reported the world over.
Not really looking for a fix but does anyone how to build binutils and all without having to generate that texinfo junk? No one uses that stuff and it just wastes space and makes builds fail all the time.
Comments
I don't think we want to do that. It appears that the texinfo stuff also goes into the man pages.
So? online man pages
If you don't have X11/Quartz/whatever or Lynx, then download the man pages from somewhere (or copy them from someone for which texinfo actually works) and then install them manually.
Does anyone know what exactly the problem with texinfo is? Why does it never work? Over half of my build failures (mostly under Fink on OSX) were caused by texinfo being stupid.
Where's the Propeller documentation there? It's not.
texinfo is great. I just don't like it getting in the way all the time. All I want to know is how to make it optional.