From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] What now?
Date: Wed, 21 Jan 2009 15:55:42 +0100 [thread overview]
Message-ID: <20090121155542.7b6cd0ec@surf> (raw)
In-Reply-To: <877i4pwzmu.fsf@macbook.be.48ers.dk>
Le Tue, 20 Jan 2009 20:23:05 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> It should, otherwise nothing else could get build.
>
> Have a look in build_<arch>/staging_dir/usr/bin, and use that compiler
> to compile your applications.
See also
http://buildroot.uclibc.org/buildroot.html#toolchain_standalone for
more details.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2009-01-21 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 18:44 [Buildroot] What now? Dave Tucker
2009-01-20 19:23 ` Peter Korsgaard
2009-01-21 14:55 ` Thomas Petazzoni [this message]
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=20090121155542.7b6cd0ec@surf \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.