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 22:36:59 +0100	[thread overview]
Message-ID: <4BEB1F7B.8010301@carallon.com> (raw)
In-Reply-To: <201005122319.35163.yann.morin.1998@anciens.enib.fr>


>> Should you even be able to set
>> thread library when using an external toolchain?
>>      
> An external toolchain can be built to not support threading. It's an option
> in crosstool-NG, at least. Maybe other means to build toolchain also offer
> this possibility.
>
> So yes, we also have to select threading model in buildroot, and it has to
> match the external toolchain capabilities.
>
>    

I understand that options that affect packages have to be set the same. 
I can also see that you need to know if the toolchain supports threads 
or not, however once you have an external toolchain surely the packages 
you build with it do not care what version of threading is used.

If you need to tell buildroot the type of threading used (linuxthread 
old/new or nptl) then currently buildroot does not check that they match 
up, as I have an nptl toolchain but am unable to select that in 
buildroot so it is set to linuxthreads new, but I got no error.

  parent reply	other threads:[~2010-05-12 21:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 17:15 [Buildroot] Status of external toolchain support Will Wagner
2010-05-12 21:19 ` 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 [this message]
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=4BEB1F7B.8010301@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