From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] building native gcc for target
Date: Wed, 8 Aug 2012 08:57:04 +0300 [thread overview]
Message-ID: <20120808055704.GA9185@sapphire.tkos.co.il> (raw)
In-Reply-To: <5021CE95.9000808@sri.com>
Hi Scott, Kevin,
On Tue, Aug 07, 2012 at 07:27:33PM -0700, Scott Moore wrote:
> On 8/7/12 7:19 PM, Steve Calfee wrote:
> >On Tue, Aug 7, 2012 at 6:18 PM, Kevin Broch <kevbroch@gmail.com> wrote:
> >>I'm am looking to build a complete (gcc too) development environment on the
> >>target (arm) but currently don't see that this is possible.
> >>I have tried all 3 toolchain types (buildroot, cross-ng, external (linaro),
> >>but regardless I don't find gcc in output/target/usr/bin/gcc
> >>I am wondering if I am missing something?
> >>
> >>If not I am looking for any pointer on how I might do this (having never
> >>created a buildroot package).
> >>Ideally I would like to create a package that compiles Linaro GCC:
> >>https://wiki.linaro.org/WorkingGroups/ToolChain/Using/GCCNative
> >>I am imagining leveraging what is used to generate other tools like gdb,
> >>binutils, and trying to incorporate the various machine options (VFP,
> >>softfloat, etc)
> >>in the configure options.
> >>
> >>Any pointers would be appreciated.
> >I guess you haven't seen how to do it because it is kind of bizarre.
> >You want to cross compile a native mode compiler. Why?
> >
> >Most people building embedded systems don't want to compile on those
> >systems. I don't know how you even bootstrap a gcc build in a system
> >without a c compiler.
> According to http://www.uclibc.org/toolchains.html (which
> unfortunately seems quite out of date), this is a recommended way of
> creating a development system for using uClibc.
> I'm actually trying to do something similar to easily build
> applications in a "clean" environment with only uClibc headers, etc,
> and also having trouble. Has anyone done this recently? (See my
> message earlier today about a configuration for x86_64)
>
> Kevin, you may need to select GCC in the "package selection for
> target -> development tools" options in menuconfig (which requires
> setting development files on target to true in build options). I've
> gotten that far but the resulting native compiler hasn't worked
> reliably.
You may try Aboriginal Linux (http://landley.net/aboriginal/) which includes
pre-built native compilers for various targets, along with their build
scripts.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2012-08-08 5:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 1:18 [Buildroot] building native gcc for target Kevin Broch
2012-08-08 2:19 ` Steve Calfee
2012-08-08 2:27 ` Scott Moore
2012-08-08 5:57 ` Baruch Siach [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2014-12-29 13:27 Boris Lenin
2014-12-29 13:34 ` 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=20120808055704.GA9185@sapphire.tkos.co.il \
--to=baruch@tkos.co.il \
--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