Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Status of external toolchain support
Date: Wed, 12 May 2010 18:15:38 +0100	[thread overview]
Message-ID: <4BEAE23A.2000906@carallon.com> (raw)

I am starting work on a new target and thought I'd take a look at using 
a crosstool-NG external toolchain and I have a couple of questions about 
what is supposed to be supported.

I have successfully built an arm toolchain using eglibc and nptl (Thanks 
Yann!).

When configuring buildroot I set all my options the same as the 
toolchain, except for thread support where nptl was not an option. Does 
it matter that they don't match up? Should you even be able to set 
thread library when using an external toolchain?

When using crosstools who should build gdb? If buildroot builds it I 
have to make sure my toolchain is not read only? Can I just let 
crosstools build gdb for the host and only get buildroot to make gdb-server?

Thanks
Will

             reply	other threads:[~2010-05-12 17:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 17:15 Will Wagner [this message]
2010-05-12 21:19 ` [Buildroot] Status of external toolchain support Yann E. MORIN
2010-05-12 21:34   ` Grant Edwards
2010-05-12 21:53     ` Yann E. MORIN
2010-05-12 22:09       ` Grant Edwards
2010-05-12 21:36   ` Will Wagner
2010-05-12 21:47     ` Yann E. MORIN
2010-05-13 12:29       ` Mark Fisher
2010-05-13 15:22 ` Thomas Petazzoni
2010-05-13 17:21   ` Yann E. MORIN
2010-05-13 20:08     ` Thomas Petazzoni
2010-05-13 20:26       ` Yann E. MORIN

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=4BEAE23A.2000906@carallon.com \
    --to=will_wagner@carallon.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