All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] openpgm: disable on AVR32
Date: Sun, 3 Nov 2013 12:18:51 +0100	[thread overview]
Message-ID: <20131103121851.2d2cc3b0@skate> (raw)
In-Reply-To: <52762F23.9010202@gmail.com>

Dear Alexander Lukichev,

On Sun, 03 Nov 2013 13:10:27 +0200, Alexander Lukichev wrote:

> >>   config BR2_PACKAGE_ZEROMQ_PGM
> >>       bool "PGM/EPGM support"
> >>       depends on BR2_PACKAGE_ZEROMQ
> >> +    depends on !BR2_avr32
> >  zeromq has a lot of reverse dependencies: cppzmq, czmq, filemq,
> > mongrel2, [python-pyzmq not necessary because python needs MMU], [zmqpp
> > already disabled for avr32]. And there's one more transitive dependency
> > to zyre. So all these should also be disabled.
> 
> I do not understand. Why should they be disabled? This patch does not
> disable the zeromq library, merely PGM support in it. I may be mistaken
> but "users" of zeromq that we have in Buildroot do not actually require
> this feature (PGM support). Or am I missing the point?

You're correct, I believe Arnout missed the fact that the dependency is
added on a sub-option of the ZeroMQ package, and not on the ZeroMQ
package itself, and there is nothing that selects
BR2_PACKAGE_ZEROMQ_PGM.

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

  reply	other threads:[~2013-11-03 11:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31  8:59 [Buildroot] [PATCH 1/1] openpgm: disable on AVR32 Alexander Lukichev
2013-10-31 17:39 ` Arnout Vandecappelle
2013-11-03 11:10   ` Alexander Lukichev
2013-11-03 11:18     ` Thomas Petazzoni [this message]
2013-11-03 17:46       ` Arnout Vandecappelle
2013-11-01 14:37 ` 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=20131103121851.2d2cc3b0@skate \
    --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.