All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Blackfin Buildroot toolchain issue
Date: Tue, 17 Mar 2015 22:55:59 +0100	[thread overview]
Message-ID: <20150317225559.4e539db9@free-electrons.com> (raw)
In-Reply-To: <20150317213403.GC21001@waldemar-brodkorb.de>

Dear Waldemar Brodkorb,

On Tue, 17 Mar 2015 22:34:03 +0100, Waldemar Brodkorb wrote:

> My opinion on this is, that there are systems supporting threads
> with uClibc, which do not have TLS support. Linuxthreads.old does
> not make use of TLS. When you build for coldfire or ARM noMMU, tls 
> is not available and it should be disabled while configuring gcc.

Sure, but we don't have to make this an option. The plan is to enable
TLS only when available.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-03-17 21:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15 21:17 [Buildroot] Blackfin Buildroot toolchain issue Thomas Petazzoni
2015-03-15 21:18 ` Thomas Petazzoni
2015-03-17 14:20   ` Gustavo Zacarias
2015-03-17 14:30     ` Thomas Petazzoni
2015-03-17 15:08       ` Gustavo Zacarias
2015-03-17 15:13         ` Thomas Petazzoni
2015-03-17 17:55           ` Gustavo Zacarias
2015-03-17 21:34             ` Waldemar Brodkorb
2015-03-17 21:55               ` Thomas Petazzoni [this message]
2015-03-17 23:00                 ` Waldemar Brodkorb
2015-03-17 13:45 ` Gustavo Zacarias
2015-03-17 13:49   ` Thomas Petazzoni
2015-03-17 14:40     ` Gustavo Zacarias
2015-03-17 14:43       ` Thomas Petazzoni
2015-03-17 16:41         ` Gustavo Zacarias

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=20150317225559.4e539db9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.