Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rabbitmq-c: needs a toolchain with posix_spawn support
Date: Tue, 12 Jan 2016 21:50:52 +0100	[thread overview]
Message-ID: <20160112205052.GB3463@free.fr> (raw)
In-Reply-To: <20160112213943.60b8fc12@free-electrons.com>

Joris, thomas, All,

On 2016-01-12 21:39 +0100, Thomas Petazzoni spake thusly:
> On Mon, 11 Jan 2016 13:52:33 +0100, Joris Lijssens wrote:
> > Fixes:
> > http://autobuild.buildroot.net/results/a6c3e79c61c5a535970d03bf37b068349f766a7f/
> > Signed-off-by: Joris Lijssens <joris.lijssens@gmail.com>
[--SNIP--]
> > diff --git a/package/rabbitmq-c/Config.in b/package/rabbitmq-c/Config.in
> > index b330c90..ec72f82 100644
> > --- a/package/rabbitmq-c/Config.in
> > +++ b/package/rabbitmq-c/Config.in
> > @@ -1,11 +1,15 @@
> >  config BR2_PACKAGE_RABBITMQ_C
> >  	bool "rabbitmq-c"
> >  	depends on BR2_TOOLCHAIN_HAS_THREADS
> > +	depends on (BR2_UCLIBC_VERSION_SNAPSHOT || BR2_UCLIBC_VERSION_NG \
> > +		|| BR2_TOOLCHAIN_USES_GLIBC) # spawn.h
> >  	help
> >  	  This is a C-language AMQP client library for use with v2.0+
> >  	  of the RabbitMQ broker.
> >  
> >  	  https://github.com/alanxz/rabbitmq-c
> >  
> > -comment "rabbitmq-c needs a toolchain w/ threads"
> > -	depends on !BR2_TOOLCHAIN_HAS_THREADS
> > +comment "rabbitmq-c needs a uclibc snapshot, uclibc-ng or (e)glibc toolchain w/ threads"
> > +	depends on !BR2_TOOLCHAIN_HAS_THREADS \
> > +		|| !(BR2_UCLIBC_VERSION_SNAPSHOT || BR2_UCLIBC_VERSION_NG \
> > +		|| BR2_TOOLCHAIN_USES_GLIBC) 
> 
> I know that the vlc package is doing the same for its spawn.h
> dependency, but I don't like this: the comment says that you need a
> "uclibc snapshot or uclibc-ng toolchain", but in practice, if you use
> an external toolchain that uses uClibc-ng, you still won't be able to
> enable the rabbitmq-c package because BR2_UCLIBC_VERSION_NG is a symbol
> that is specific to the internal toolchain backend.
> 
> So I see a few options here:
> 
>  1/ We do like the blktrace package is doing (for the same reason),
>     which is allowing the package only on glibc and musl
>     configurations. This is a bit sad because modern uClibc version are
>     perfectly capable of handling this package.
> 
>  2/ We assume that all uClibc versions are now sufficiently recent and
>     we allow the package with uClibc, with a special exception for the
>     Blackfin toolchain (which was the reason of the failure).
> 
> (If we chose either (1) or (2), then we should align vlc and blktrace
> on the chosen solution)
> 
> Peter, Yann, what do you think ?

Well:
  - I don't care much about bfin, 

  - last uClibc verison was ~3 years ago, uClibc snapshot is OK,
    uClibc-ng is capable.

So we can consider that ancient uClibc missing spawn.h is too old, and
we don't support that.

So I'm fine with #2. And of course, we must propagate that decision ot
other similarly-impacted packages, yes.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2016-01-12 20:50 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 [this message]
2016-01-13  7:56     ` Joris Lijssens
2016-01-13  8:17       ` Thomas Petazzoni

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=20160112205052.GB3463@free.fr \
    --to=yann.morin.1998@free.fr \
    --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