From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] building native gcc for target
Date: Mon, 29 Dec 2014 14:34:02 +0100 [thread overview]
Message-ID: <20141229143402.55e5900d@free-electrons.com> (raw)
In-Reply-To: <CAHBHQYO9BLD1tJKxaR3z5StYXEtUvwBwQZfFNSzpZEcqHyR4gg@mail.gmail.com>
Dear Boris Lenin,
On Mon, 29 Dec 2014 15:27:40 +0200, Boris Lenin wrote:
> I want to have a gcc binary in my target, so I can compile ELFs inside it.
> This is for compiling using uClibc as suggested here:
> http://www.uclibc.org/toolchains.html
>
> But after I make, I have no gcc in output/target/usr/bin/gcc
> I also don't have an option to include gcc in menuconfig->Target
> packages->Development Tools
>
> How can I have a working gcc that's using uClibc inside my new rootfs?
This is no longer supported in Buildroot. See
http://buildroot.org/downloads/manual/manual.html#faq-no-compiler-on-target
for more details about this topic.
You should either cross-compile your applications/libraries, or use a
full-featured Linux distribution on your system.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-29 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 13:27 [Buildroot] building native gcc for target Boris Lenin
2014-12-29 13:34 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-08 1:18 Kevin Broch
2012-08-08 2:19 ` Steve Calfee
2012-08-08 2:27 ` Scott Moore
2012-08-08 5:57 ` Baruch Siach
2012-08-08 20:24 ` Kevin Broch
2012-08-09 3:32 ` Baruch Siach
2012-08-10 2:28 ` Kevin Broch
2012-08-08 13:58 ` Grant Edwards
2012-08-08 20:16 ` Kevin Broch
2012-08-11 18:16 ` Thomas Petazzoni
2012-08-14 0:38 ` Kevin Broch
2012-08-08 20:49 ` Kevin Broch
2012-08-08 21:55 ` Alex Bradbury
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=20141229143402.55e5900d@free-electrons.com \
--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