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] [PATCH] rabbitmq-c: needs a toolchain with posix_spawn support
Date: Wed, 13 Jan 2016 09:17:26 +0100	[thread overview]
Message-ID: <20160113091726.62ed0d01@free-electrons.com> (raw)
In-Reply-To: <CACt6We3dS-9LNNTMkUNu2vmBdSkJYri6g6X0g2No-D61GRmq4g@mail.gmail.com>

Dear Joris Lijssens,

On Wed, 13 Jan 2016 08:56:33 +0100, Joris Lijssens wrote:

> So I will send a new patch excluding the blackfin. are there still other
> configurations that use an ancient uClibc without spawn support, or is the
> blackfin the only one?

As far as I remember, Blackfin is the only one.

Best regards,

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

      reply	other threads:[~2016-01-13  8:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 12:52 [Buildroot] [PATCH] rabbitmq-c: needs a toolchain with posix_spawn support Joris Lijssens
2016-01-12 20:39 ` Thomas Petazzoni
2016-01-12 20:50   ` Peter Korsgaard
2016-01-12 20:50   ` Yann E. MORIN
2016-01-13  7:56     ` Joris Lijssens
2016-01-13  8:17       ` Thomas Petazzoni [this message]

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=20160113091726.62ed0d01@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