public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: David Fernandez <dfernandez@solarflare.com>
To: <insight@sourceware.org>
Subject: release tarballs and cvs 6.8 branch failing to build due to texi errors.
Date: Thu, 13 Feb 2014 14:31:00 -0000	[thread overview]
Message-ID: <52FCD72B.7050606@solarflare.com> (raw)

Hi there,

I've tried the 6.8-1a ftp tarball in releases, and also the cvs 6.8 
branch, to build avr-gdb, and I get this quite early during make all:

Making info in doc
make[3]: Entering directory `/home/df/build/insight/avr/bfd/doc'
restore=: && backupdir=".am$$" && \
rm -rf $backupdir && mkdir $backupdir && \
if (makeinfo --split-size=5000000 --split-size=5000000 --version) 
 >/dev/null 2>&1; then \
   for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] bfd.i[0-9] 
bfd.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 --split-size=5000000   -I 
/home/df/src/insight-6.8-1/bfd/doc \
  -o bfd.info `test -f 'bfd.texinfo' || echo 
'/home/df/src/insight-6.8-1/bfd/doc/'`bfd.texinfo; \
then \
   rc=0; \
else \
   rc=$?; \
   $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/home/df/src/insight-6.8-1/bfd/doc/bfd.texinfo:326: unknown command 
`colophon'
/home/df/src/insight-6.8-1/bfd/doc/bfd.texinfo:337: unknown command `cygnus'
/home/df/src/insight-6.8-1/bfd/doc/elf.texi:11: raising the section 
level of @subsubsection which is too low
make[3]: *** [bfd.info] Error 1
make[3]: Leaving directory `/home/df/build/insight/avr/bfd/doc'

May be there is a quick fix to try?

Regards.
David

                 reply	other threads:[~2014-02-13 14:31 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=52FCD72B.7050606@solarflare.com \
    --to=dfernandez@solarflare.com \
    --cc=insight@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).