From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] daemon: new package
Date: Tue, 2 May 2017 22:49:47 +0200 [thread overview]
Message-ID: <20170502224947.16429ddc@free-electrons.com> (raw)
In-Reply-To: <fbdaa88f9b37850b3c15e3f0c521ef4d225a2eb9.1493701664.git.baruch@tkos.co.il>
Hello,
On Tue, 2 May 2017 08:07:44 +0300, Baruch Siach wrote:
> +config BR2_PACKAGE_DAEMON
> + bool "daemon"
> + depends on BR2_USE_MMU # fork()
> + depends on BR2_TOOLCHAIN_HAS_THREADS
> + help
> + Daemon turns other process into daemons.
> +
> + http://www.libslack.org/daemon/
> +
> +comment "daemon needs a toolchain w/ threads"
depends on BR2_USE_MMU
was missing here.
> + depends on !BR2_TOOLCHAIN_HAS_THREADS
Committed with this minor issue fixed. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-02 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 5:07 [Buildroot] [PATCH] daemon: new package Baruch Siach
2017-05-02 20:49 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-01 19:17 Baruch Siach
2017-05-01 19:33 ` Romain Naour
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=20170502224947.16429ddc@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