From: Samir <samir.rawal@tokheimkaizen.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to test Buildroot component
Date: Mon, 7 May 2007 10:05:42 +0530 [thread overview]
Message-ID: <MAILmRf6Ci6nx8dyDd300000030@mail.tokheimkaizen.com> (raw)
Dear All
I am building a Cross-development tool chain using Buildroot.
How to test the component generated by build root. Like GCC, Binutils &
uClibc Library.
Samir Raval
(R&D Department)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20070507/51220a1d/attachment.htm
reply other threads:[~2007-05-07 4:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=MAILmRf6Ci6nx8dyDd300000030@mail.tokheimkaizen.com \
--to=samir.rawal@tokheimkaizen.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