Hi Karl, Thank you for responding.
> Something else must have been going on. It wouldn’t surprise me if the installation of the TeX Live package on the host system was purely coincidental. So far every issue up until this one has been caused by an error on my part (typo, mistaken assumptions, and etc.) with an identifiable cause. Why shouldn't this one be as well? If helpful I’d be willing to try to reproduce the texinfo build error, upload the configuration log, and build output. As well as any other information that would be needed. I’ve kept a detailed log of every command issued for each step. The host OS (Debian 7.x) is a VM that’s easily replicated. Kind Regards & Happy Holidays! Graham On Dec 24, 2014, at 4:53 PM, Karl Berry <[email protected]> wrote: > Hi Graham, > > Thanks for the note. > > The solution is to install a tex system such as texlive. > > I can't understand why that is the solution. TeX Live has nothing to do > with makedoc. makedoc is a tiny self-contained program in the info/ > subdirectory of the texinfo source. It has to be built and run > natively, rather than cross. There is code in texinfo's configure[.ac] > to automatically do a subsidiary native configure and build to handle > makedoc. > > I don't doubt the situation can be improved, but installing TeX Live > can't be the answer wrt makedoc. Something else must have been going on. > > Best, > Karl > > P.S. Gavin, I wonder if we could get rid of the whole cross-compiling > native_tools/TOOLS_ONLY complexity by replacing the C implementation of > makedoc with a Perl/whatever implementation that does not need to be > compiled. Just if you feel like looking into it ...
