public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Carlos Valiente <carlos@pepelabs.net>
To: cgen@sourceware.org
Subject: cgen/doc/running.texi: Fix documentation build
Date: Tue, 28 Oct 2014 19:04:00 -0000	[thread overview]
Message-ID: <f1d297cda75c1f86b54359f84d94da6a@pepelabs.net> (raw)

Hi! My version of `makeinfo` (5.2) fails to build the documentation 
because of the `@subsection Set up the arguments for cgen` line in 
`cgen/doc/running.texi`:

     $ make info
     restore=: && backupdir=".am$$" && \
             rm -rf $backupdir && mkdir $backupdir && \
             if (makeinfo --split-size=5000000 --version) >/dev/null 
2>&1; then \
               for f in cgen.info cgen.info-[0-9] cgen.info-[0-9][0-9] 
cgen.i[0-9] cgen.i[0-9][0-9]; do \
                 if test -f $f; then mv $f $backupdir; restore=mv; else 
:; fi; \
               done; \
             else :; fi && \
             if makeinfo --split-size=5000000   -I ../.././cgen/doc \
              -o cgen.info `test -f 'cgen.texi' || echo 
'../.././cgen/doc/'`cgen.texi; \
             then \
               rc=0; \
             else \
               rc=$?; \
               $restore $backupdir/* `echo "./cgen.info" | sed 
's|[^/]*$||'`; \
             fi; \
             rm -rf $backupdir; exit $rc
     ./running.texi:19: raising the section level of @subsection which is 
too low
     make: *** [cgen.info] Error 1
     $

When that line is removed, the documentation can be built:

     diff --git a/cgen/doc/running.texi b/cgen/doc/running.texi
     index a435405..0b76f49 100644
     --- a/cgen/doc/running.texi
     +++ b/cgen/doc/running.texi
      @@ -16,8 +16,6 @@ The main tasks of this script are to:
      @item Apply any post processing to the output files.
      @end enumerate

     -@subsection Set up the arguments for cgen.
     -
      CGEN takes several standard arguments.
      Each application can then add its own arguments.
      By convention generic CGEN options are lowercase letters

Is there a better way of fixing this issue?

C



                 reply	other threads:[~2014-10-28 19:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f1d297cda75c1f86b54359f84d94da6a@pepelabs.net \
    --to=carlos@pepelabs.net \
    --cc=cgen@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).