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] dialog: bump to version 1.2-20150125
Date: Sat, 21 Feb 2015 14:07:52 +0100	[thread overview]
Message-ID: <20150221140752.3aa8449b@free-electrons.com> (raw)
In-Reply-To: <1424519547-16093-1-git-send-email-gustavo@zacarias.com.ar>

Dear Gustavo Zacarias,

On Sat, 21 Feb 2015 08:52:27 -0300, Gustavo Zacarias wrote:
> And drop thread requirement, it's really not necessary.
> For python-dialog that was already inherent in python itself.
> 
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>

Applied to next, thanks. Interestingly, it's you who added this thread
dependency because dialog needs MMU. And Peter applied the patch. See:

commit 9d9d842d871b8645f70c3a90f59f8e2e09935656
Author: Gustavo Zacarias <gustavo@zacarias.com.ar>
Date:   Fri Dec 28 00:59:00 2012 +0000

    dialog: needs mmu
    
    Fixes
    http://autobuild.buildroot.net/results/b673ef6d6315dc5df77e000199a63f90904829d5
    
    Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
    Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>

diff --git a/package/dialog/Config.in b/package/dialog/Config.in
index 9d3462e..db5197f 100644
--- a/package/dialog/Config.in
+++ b/package/dialog/Config.in
@@ -1,5 +1,6 @@
 config BR2_PACKAGE_DIALOG
        bool "dialog"
+       depends on BR2_TOOLCHAIN_HAS_THREADS # fork()
        select BR2_PACKAGE_NCURSES
        select BR2_PACKAGE_LIBICONV if !BR2_ENABLE_LOCALE
        help

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

  reply	other threads:[~2015-02-21 13:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21 11:52 [Buildroot] [PATCH] dialog: bump to version 1.2-20150125 Gustavo Zacarias
2015-02-21 13:07 ` Thomas Petazzoni [this message]
2015-02-21 13:17   ` 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=20150221140752.3aa8449b@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