public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Kaoru Fukui <k_fukui@highway.ne.jp>
To: <insight@sources.redhat.com>
Subject: makeinfo problem
Date: Mon, 03 Sep 2001 07:49:00 -0000	[thread overview]
Message-ID: <20010903234623.Postino-025780@smtp01.highway.ne.jp> (raw)

Hi!

I got insight source from cvs today.
Problem is that.
My texinfo is texinfo-4.0b-3.src.rpm from rawhide.
My system is linuxppc.

Any help

Kaoru

----------------------------------------------------------------
make[1]: Leaving directory `/usr/src/redhat/BUILD/src/sim'
make[1]: Entering directory `/usr/src/redhat/BUILD/src/gdb'
make[2]: Entering directory `/usr/src/redhat/BUILD/src/gdb'
make[3]: Entering directory `/usr/src/redhat/BUILD/src/gdb/doc'
echo "@set GDBVN `head -1 ./../version.in`" > ./GDBvn.new
mv GDBvn.new GDBvn.texi
(test "$LN_S" = "ln -s" && \
  ln -s ./all-cfg.texi gdb-cfg.texi) || \
ln ./all-cfg.texi gdb-cfg.texi || \
cp ./all-cfg.texi gdb-cfg.texi
makeinfo  -I ./../../readline/doc -I ./../mi -I . -o ./gdb.info gdb.texinfo
gdb.texinfo:6326: No matching `@end itemize'.
./../../readline/doc/rluser.texinfo:1331: warning: @sc argument all uppercase, 
thus no effect.
makeinfo: Removing output file `./gdb.info' due to errors; use --force to preserve.
make[3]: *** [gdb.info] Error 2
make[3]: Leaving directory `/usr/src/redhat/BUILD/src/gdb/doc'
make[2]: *** [subdir_do] Error 1
make[2]: Leaving directory `/usr/src/redhat/BUILD/src/gdb'
make[1]: *** [info] Error 2
make[1]: Leaving directory `/usr/src/redhat/BUILD/src/gdb'
make: *** [do-info] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.1235 (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.1235 (%build)
[root@g4mpKFUKUI SPECS]# 


             reply	other threads:[~2001-09-03  7:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03  7:49 Kaoru Fukui [this message]
2001-09-04  7:25 ` Keith Seitz

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=20010903234623.Postino-025780@smtp01.highway.ne.jp \
    --to=k_fukui@highway.ne.jp \
    --cc=insight@sources.redhat.com \
    /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).