Fix "make html" and "make pdf" for libgloss

[Jeff Johnston]

Patch checked in.

Thanks,

-- Jeff J.

Joseph S. Myers wrote:
> This patch adds support for the "html" and "pdf" targets to libgloss, to 
> build documentation in those formats, and fixes some problems with the 
> libgloss manual that stopped the PDF build from working (subsections 
> should not be directly below chapters).  OK to commit?
>
> 2009-06-19  Joseph Myers  <joseph@codesourcery.com>
>
> 	* Makefile.in (html, pdf): New.
> 	* doc/Makefile.in (html, pdf, porting.pdf, porting.html): New.
> 	* doc/porting.texi: Fix section structure.
>
> Index: libgloss/Makefile.in
> ===================================================================
> RCS file: /cvs/src/src/libgloss/Makefile.in,v
> retrieving revision 1.5
> diff -u -r1.5 Makefile.in
> --- libgloss/Makefile.in	7 Jan 2009 22:10:28 -0000	1.5
> +++ libgloss/Makefile.in	19 Jun 2009 16:48:24 -0000
> @@ -155,7 +155,7 @@
>  	$(MAKE) DO=$@ DODIRS="$(SUBDIRS)" $(FLAGS_TO_PASS) subdir_do; \
>  	$(MULTICLEAN) multi-clean DO=$@
>  
> -.PHONY: info install-info clean-info
> +.PHONY: info install-info clean-info html pdf
>  subdir_do:
>  	@rootpre=`pwd`/; export rootpre; \
>  	srcrootpre=`cd $(srcdir); pwd`/; export srcrootpre; \
> @@ -171,7 +171,7 @@
>  	  else true; fi; \
>  	done
>  
> -info dvi docs:
> +info dvi html pdf docs:
>  	rootpre=`pwd`/; export rootpre; \
>  	srcrootpre=`cd $(srcdir); pwd`/; export srcrootpre; \
>  	$(MAKE) DO=$@ DODIRS=doc $(FLAGS_TO_PASS) subdir_do
> Index: libgloss/doc/Makefile.in
> ===================================================================
> RCS file: /cvs/src/src/libgloss/doc/Makefile.in,v
> retrieving revision 1.3
> diff -u -r1.3 Makefile.in
> --- libgloss/doc/Makefile.in	7 Jan 2009 22:10:29 -0000	1.3
> +++ libgloss/doc/Makefile.in	19 Jun 2009 16:48:24 -0000
> @@ -39,8 +39,12 @@
>  
>  info:	porting.info 
>  
> +html:	porting.html
> +
>  dvi:	porting.dvi 
>  
> +pdf:	porting.pdf
> +
>  ps:	porting.ps 
>  
>  doc:	info dvi
> @@ -53,10 +57,16 @@
>  porting.dvi: $(srcdir)/porting.texi $(srcdir)/porting.texi
>  	$(TEXI2DVI) $(srcdir)/porting.texi
>  
> +porting.pdf: $(srcdir)/porting.texi $(srcdir)/porting.texi
> +	$(TEXI2DVI) --pdf $(srcdir)/porting.texi
> +
>  # info file for online browsing
>  porting.info: $(srcdir)/porting.texi $(srcdir)/porting.texi
>  	$(MAKEINFO) -I $(srcdir) -o porting.info $(srcdir)/porting.texi
>  
> +porting.html: $(srcdir)/porting.texi $(srcdir)/porting.texi
> +	$(MAKEINFO) --html -I $(srcdir) -o porting.html $(srcdir)/porting.texi
> +
>  porting.ps: porting.dvi
>  	dvips -f porting.dvi > porting.ps
>  		
> Index: libgloss/doc/porting.texi
> ===================================================================
> RCS file: /cvs/src/src/libgloss/doc/porting.texi,v
> retrieving revision 1.2
> diff -u -r1.2 porting.texi
> --- libgloss/doc/porting.texi	18 Apr 2006 16:14:57 -0000	1.2
> +++ libgloss/doc/porting.texi	19 Jun 2009 16:48:24 -0000
> @@ -135,7 +135,7 @@
>  @end menu
>  
>  @node Supported targets, Building libgloss, Libgloss, Libgloss
> -@subsection Supported Targets
> +@section Supported Targets
>  Currently libgloss is being used for the following targets:
>  
>  @menu
> @@ -233,7 +233,7 @@
>  mostly for Unix based systems. 
>  
>  @node Building libgloss, Board support, Supported targets, Libgloss
> -@subsection Configuring and building libgloss.
> +@section Configuring and building libgloss.
>  
>  Libgloss uses an autoconf based script to configure. Autoconf scripts
>  are portable shell scripts that are generated from a configure.in file.
> @@ -302,7 +302,7 @@
>  tools using libgloss's test suites.
>  
>  @node Board support, , Building libgloss, Libgloss
> -@subsection Adding Support for a New Board
> +@section Adding Support for a New Board
>  
>  This section explains how to add support for a new board to libgloss.
>  In order to add support for a board, you must already have developed a
> @@ -378,7 +378,7 @@
>  @end menu
>  
>  @node Overview, Options, , GCC
> -@subsection Compilation passes
> +@section Compilation passes
>  
>  GCC by itself only compiles the C or C++ code into assembler. Typically
>  GCC invokes all the passes required for you. These passes are cpp, cc1,
>
>