From: Andreas Schwab <schwab@linux-m68k.org>
To: Zhihua Che <zhihua.che@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: [Buiding Error] git version 238a89c5e410f61d2786cffca0a55dcf50325cd4
Date: Fri, 23 Mar 2012 17:45:00 -0000 [thread overview]
Message-ID: <m262dvmcui.fsf@igel.home> (raw)
In-Reply-To: <CABexPfHEj4=u-OPuTe-H1cAr4dFVgitHxOjoVCyFCW1t3ZNpGA@mail.gmail.com> (Zhihua Che's message of "Fri, 23 Mar 2012 22:10:22 +0800")
Zhihua Che <zhihua.che@gmail.com> writes:
> WARNING: `makeinfo' is missing on your system. You should only need it if
> you modified a `.texi' or `.texinfo' file, or any other file
> indirectly affecting the aspect of the manual. The spurious
> call might also be the consequence of using a buggy `make' (AIX,
> DU, IRIX). You might want to install the `Texinfo' package or
> the `GNU make' package. Grab either from any GNU archive site.
> make[3]: *** [bfd.info] Error 1
>
> Does anybody build and fail like this ever?
If you are building from the repository then makeinfo is a required
dependency. Prebuilt info files are only present in release and
snapshot tarballs.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-03-23 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 14:10 Zhihua Che
2012-03-23 17:09 ` Joel Brobecker
2012-03-23 17:45 ` Andreas Schwab [this message]
2012-03-25 12:07 ` Zhihua Che
2012-03-25 19:32 ` Andreas Schwab
[not found] ` <CABexPfHbrq2Zukp2XrepTonLhRoBVr1EAT4rZhqfaAwt7EPMVA@mail.gmail.com>
2012-03-26 2:51 ` Zhihua Che
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=m262dvmcui.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gdb@sourceware.org \
--cc=zhihua.che@gmail.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).