From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] first things first for a newbie
Date: Sun, 29 Jan 2012 14:49:29 +0100 [thread overview]
Message-ID: <20120129144929.41aeb832@skate> (raw)
In-Reply-To: <CAPEB33zWQevjj3qs0C6x4POw1qjgByXDSwAxaGdh7VEJ47wn6A@mail.gmail.com>
Hello,
[ Please don't reply to me directly: keep the list in Cc ]
Le Sun, 29 Jan 2012 13:34:03 +0000,
MERCADIER Johann <johann.mercadier@imerir.com> a ?crit :
> I just registered into IRC channel as JoM. The Doc/manual does'nt
> answer to my problem they look much more as guidelines. By the way I
> got the following problem while creating the manual:
> "
> $ make manual
> Generating HTML manual...
> /bin/bash: a2x: command not found
> make: *** [output/docs/manual/manual.html] Error 127
> "
> if you already have faced out such a mistake?
Could you read the error message? It says:
a2x: command not found
So it means that the a2x command is not available on your system, and
that you must install it. You have to install the 'asciidoc' package,
which contains the necessary utilities to compile the Buildroot
documentation.
> TC stand for Tool Chain
Ok. This is not a very common acronym.
> Sorry about that my mistake was to have created a HOST_DIR called
> 'target'... Please say nothing...So I modify that to call it
> 'workdone' til know everything work fine all options for GDB have
> been compiled out.
>
> Will proceed with the creation of a defconfig for the pandaboard.
>
> I noticed that no config file does exist for this board does it
> mean that every person who want to use it has to do those steps
> before using it? or it is mainly dependant of the buildroot version?
A Pandaboard defconfig file was submitted some time ago, but hasn't
been integrated into Buildroot (due to lack of time of the maintainer
at the moment), but it would definitely be great to have one. You can
search in the mailing list archives for the patch adding the Pandaboard
defconfig file.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-01-29 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-28 19:32 [Buildroot] first things first for a newbie MERCADIER Johann
2012-01-28 19:39 ` Yegor Yefremov
2012-01-28 21:03 ` MERCADIER Johann
2012-01-28 21:45 ` Thomas Petazzoni
[not found] ` <CAPEB33zWQevjj3qs0C6x4POw1qjgByXDSwAxaGdh7VEJ47wn6A@mail.gmail.com>
2012-01-29 13:49 ` Thomas Petazzoni [this message]
2012-01-29 14:42 ` MERCADIER Johann
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=20120129144929.41aeb832@skate \
--to=thomas.petazzoni@free-electrons.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