Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] glib 2.40 on xtensa
Date: Sun, 20 Jul 2014 10:26:11 +0200	[thread overview]
Message-ID: <20140720102611.69817922@free-electrons.com> (raw)
In-Reply-To: <CAMo8Bf+SfLYex0+040254AgNVfRM542-hoHfY355oxaw7ZWcww@mail.gmail.com>

Dear Max Filippov,

On Sun, 20 Jul 2014 04:17:53 +0400, Max Filippov wrote:

> > Argh. There's no NPTL support for:
> >
> >  - ARC (but I believe it's coming)
> >  - AVR32 (but we're deprecating this architecture, so we don't care)
> >  - Blackfin (and I don't think there's much hope to have NPTL one day,
> >    but glib is anyway disabled on !MMU platforms, so we don't care)
> >  - Xtensa (don't know)
> >  - i386 (because NPTL requires at least i486)
> >
> > Should we patch glib to make the support of the GCond stuff optional,
> > and hope not too many programs will use it? Or simply add the NPTL
> > dependency to glib, but that would mean a huge number of packages
> > suddenly become unavailable for some architectures.
> 
> There's a patch in glib mainline that implements GMutex natively on linux.
> It applies cleanly to glib-2.40 and with it xtensa builds successfully.
> I can post a buildroot patch with it.

Ah, thanks, sounds good!

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

  reply	other threads:[~2014-07-20  8:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 22:40 [Buildroot] glib 2.40 on xtensa Thomas Petazzoni
2014-07-19  0:28 ` Max Filippov
2014-07-19  9:33   ` Thomas Petazzoni
2014-07-20  0:17     ` Max Filippov
2014-07-20  8:26       ` Thomas Petazzoni [this message]
2014-07-20  0:20     ` Max Filippov

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=20140720102611.69817922@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox