Follow-up Comment #25, bug #66583 (group groff):
[comment #24 comment #24:] > [comment #23 comment #23:] >> https://savannah.gnu.org/bugs/?66609 does exactly that. The only issue it >> has is that I'm not sure how should manually disabling building the manual >> be reflected in the summary of available features that ./configure prints. >> The current state is that it prints: >> can build groff.{info,html,txt} : no >> can build groff.{dvi,pdf} : no >> as if makeinfo wasn't available. I am not sure whether this is correct >> behavior. > > Allow me to correct myself. It doesn't do even the above. It prints: > can build groff.{info,html,txt} : yes > but then doesn't build them anyway, which feels wrong. Either we could > simply print "no", or we could print something like "disabled" to clearly > distinguish it from makeinfo not being available, although it could be > argued that omission of the related warning is precisely such a distinction, > though. If we're talking about what's actually been committed to Git, I can't reproduce this. When I build on Solaris 10, where "makeinfo" is unavailable, I get this: ... checking for bison... bison -y checking for m4... m4 checking for makeinfo... no checking for texi2dvi... missing checking for tex... missing checking for ranlib... : checking for install-info... no ... GNU roff version 1.23.0.2695-cdff6 ---------------------------------------------------------------------- installation directory prefix : /home/gbranden command name prefix : g wrappers used for macro packages : an ansun bib m s v vgrind C++ compiler and options : g++ -std=gnu++11 -g -O2 -D_REENTRANT use libgroff's memory allocator : no C compiler and options : gcc -g -O2 -D_REENTRANT Perl interpreter version : 5.8.4 X11 support : enabled X11 app defaults directory : /home/gbranden/lib/X11/app-defaults default paper format : letter 'groff -l' uses print spooler : lpr use URW fonts for PDF output : no preconv can use uchardet library : no can build groff.{info,html,txt} : no can build groff.{dvi,pdf} : no ---------------------------------------------------------------------- > It prints: > can build groff.{info,html,txt} : yes > but then doesn't build them anyway, which feels wrong. The auxiliary verb "can" is not a synonym of "will". If you build from a distribution archive, which is *the* premier means of _groff_ distribution, the generated forms of our Texinfo manual are already present, and therefore would only need to be regenerated if someone modified _doc/groff.texi_. Are you familiar with the practice of distributing (compressed) tar archives when making a software release? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?66583> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
signature.asc
Description: PGP signature
