Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] building native gcc for target
Date: Wed, 8 Aug 2012 13:58:31 +0000 (UTC)	[thread overview]
Message-ID: <jvtra6$e8e$1@dough.gmane.org> (raw)
In-Reply-To: 5021CE95.9000808@sri.com

On 2012-08-08, Scott Moore <scott.moore@sri.com> wrote:
> On 8/7/12 7:19 PM, Steve Calfee wrote:
>
>> 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?
>
> 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,

I don't see why a cross compiler built using Crosstool-NG doesn't
satisfy that requirement.

-- 
Grant Edwards               grant.b.edwards        Yow! Spreading peanut
                                  at               butter reminds me of
                              gmail.com            opera!!  I wonder why?

  parent reply	other threads:[~2012-08-08 13:58 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
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 [this message]
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='jvtra6$e8e$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.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