From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] manual: prerequisite.txt: add texinfo to the mandatory package list
Date: Fri, 16 Nov 2012 07:13:32 +0100 [thread overview]
Message-ID: <1353046413-3015-1-git-send-email-s.martin49@gmail.com> (raw)
Using the internal Buildroot toolchain backend, makeinfo, whom belongs to
the texinfo package, is required to build gcc and gdb.
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
---
docs/manual/prerequisite.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/docs/manual/prerequisite.txt b/docs/manual/prerequisite.txt
index 693347b..31d437d 100644
--- a/docs/manual/prerequisite.txt
+++ b/docs/manual/prerequisite.txt
@@ -42,6 +42,7 @@ Mandatory packages
** +python+ (version 2.6 or 2.7)
** +unzip+
** +rsync+
+** +texinfo+ (required for internal Buildroot toolchain backend)
* Source fetching tools:
** +wget+
--
1.8.0
next reply other threads:[~2012-11-16 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 6:13 Samuel Martin [this message]
2012-11-16 6:13 ` [Buildroot] [PATCH 2/2] manual: contribute.txt: do not use --summary option with 'git format-patch' Samuel Martin
2012-11-16 7:44 ` [Buildroot] [PATCH 1/2] manual: prerequisite.txt: add texinfo to the mandatory package list Peter Korsgaard
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=1353046413-3015-1-git-send-email-s.martin49@gmail.com \
--to=s.martin49@gmail.com \
--cc=buildroot@busybox.net \
/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