From: Jie Zhang <jie.zhang@analog.com>
To: gdb-patches@sourceware.org
Subject: [RFA] Fix a parallel build error in doc
Date: Sun, 17 Jan 2010 01:07:00 -0000 [thread overview]
Message-ID: <4B5262AC.3080606@analog.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
Hi,
I just found this when building our Blackfin port GDB with -j4 :
makeinfo --split-size=5000000 -I
/home/jie/blackfin-sources/toolchain/trunk/binutils-2.20/gdb/doc -o
annotate.info
/home/jie/blackfin-sources/toolchain/trunk/binutils-2.20/gdb/doc/annotate.texinfo
echo "@set BUGURL @uref{http://www.gnu.org/software/gdb/bugs/}" >>
./GDBvn.new
./gdb-cfg.texi:16: @include `GDBvn.texi': No such file or directory.
if [ "@uref{http://www.gnu.org/software/gdb/bugs/}" =
"@uref{http://www.gnu.org/software/gdb/bugs/}" ]; then \
echo "@set BUGURL_DEFAULT" >> ./GDBvn.new; \
fi
mv GDBvn.new GDBvn.texi
makeinfo --split-size=5000000 -I
/home/jie/blackfin-sources/toolchain/trunk/binutils-2.20/gdb/doc/../../readline/doc
-I
/home/jie/blackfin-sources/toolchain/trunk/binutils-2.20/gdb/doc/../mi
-I /home/jie/blackfin-sources/toolchain/trunk/binutils-2.20/gdb/doc \
-o gdb.info
/home/jie/blackfin-sources/toolchain/trunk/binutils-2.20/gdb/doc/gdb.texinfo
Making install in doc
makeinfo: Removing output file `annotate.info' due to errors; use
--force to preserve.
make[3]: *** [annotate.info] Error 1
We should also add GDBvn.texi in ANNOTATE_DOC_BUILD_INCLUDES, shouldn't we?
Is the attached patch OK?
Thanks,
Jie
[-- Attachment #2: gdb-doc-makefile-fix-annotate-dep.diff --]
[-- Type: text/x-diff, Size: 605 bytes --]
* Makefile.in (ANNOTATE_DOC_BUILD_INCLUDES): Add GDBvn.texi.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/doc/Makefile.in,v
retrieving revision 1.48
diff -u -p -r1.48 Makefile.in
--- Makefile.in 1 Jan 2010 07:31:48 -0000 1.48
+++ Makefile.in 17 Jan 2010 00:59:29 -0000
@@ -147,7 +147,8 @@ STABS_DOC_FILES = \
ANNOTATE_DOC_SOURCE_INCLUDES = \
$(srcdir)/fdl.texi
ANNOTATE_DOC_BUILD_INCLUDES = \
- gdb-cfg.texi
+ gdb-cfg.texi \
+ GDBvn.texi
ANNOTATE_DOC_FILES = \
$(srcdir)/annotate.texinfo \
$(ANNOTATE_DOC_SOURCE_INCLUDES) \
next reply other threads:[~2010-01-17 1:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 1:07 Jie Zhang [this message]
2010-01-18 3:38 ` Joel Brobecker
2010-01-18 3:41 ` Jie Zhang
2010-01-18 3:59 ` Joel Brobecker
2010-01-18 4:00 ` Jie Zhang
2010-01-18 4:17 ` Joel Brobecker
2010-01-18 4:28 ` Jie Zhang
2010-01-18 5:01 ` Joel Brobecker
2010-01-18 6:53 ` Jie Zhang
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=4B5262AC.3080606@analog.com \
--to=jie.zhang@analog.com \
--cc=gdb-patches@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