From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] knock: new package
Date: Tue, 10 Sep 2013 22:58:53 +0200 [thread overview]
Message-ID: <522F880D.1090904@mind.be> (raw)
In-Reply-To: <CAAXf6LWfhUhQ2pRwaFh6szZ=51WfPPJNB2AVwzoodV0w4XT4DQ@mail.gmail.com>
On 08/09/13 16:32, Thomas De Schampheleire wrote:
> Another tip: for these type of dependency problems, you could also use
> an external toolchain, like the Sourcery ones, to get much quicker
> results. With such external toolchains, it also becomes very easy to
> test some other architectures like powerpc, arm, ...
And you can also use the toolchains used by the autobuilders, to test
with uClibc-based toolchains.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-09-10 20:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 21:33 [Buildroot] [PATCH 1/3] knock: new package Michael Rommel
2013-09-01 21:33 ` [Buildroot] [PATCH 2/3] aiccu: " Michael Rommel
2013-09-02 8:28 ` Thomas De Schampheleire
2013-09-02 8:57 ` Thomas Petazzoni
2013-09-02 23:49 ` Michael Rommel
2013-09-01 21:33 ` [Buildroot] [PATCH 3/3] python-pyzmq: " Michael Rommel
2013-09-02 8:24 ` Thomas De Schampheleire
2013-09-02 15:55 ` Arnout Vandecappelle
2013-09-03 18:04 ` Michael Rommel
2013-09-03 21:30 ` Arnout Vandecappelle
2013-09-08 12:07 ` [Buildroot] [PATCH 1/3] knock: " Thomas De Schampheleire
2013-09-08 12:08 ` Thomas De Schampheleire
[not found] ` <E9670545-EE12-445D-A15C-C0C3E4A4116A@layer-7.net>
2013-09-08 14:09 ` Michael Rommel
2013-09-08 14:32 ` Thomas De Schampheleire
2013-09-10 20:58 ` Arnout Vandecappelle [this message]
2013-09-15 18:18 ` Thomas Petazzoni
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=522F880D.1090904@mind.be \
--to=arnout@mind.be \
--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