Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/rsyslog: needs MMU (fork)
Date: Wed, 14 May 2014 21:38:16 +0300	[thread overview]
Message-ID: <20140514183816.GI4096@tarshish> (raw)
In-Reply-To: <1400092133-16971-2-git-send-email-bernd.kuhls@t-online.de>

Hi Bernd,

On Wed, May 14, 2014 at 08:28:53PM +0200, Bernd Kuhls wrote:
> fixes http://autobuild.buildroot.net/results/5c0/5c03bf3a1e4e922a18b40f854ff59d905a93a89f/
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
>  package/rsyslog/Config.in |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/package/rsyslog/Config.in b/package/rsyslog/Config.in
> index 8a84fea..82a6922 100644
> --- a/package/rsyslog/Config.in
> +++ b/package/rsyslog/Config.in
> @@ -8,6 +8,7 @@ config BR2_PACKAGE_RSYSLOG
>  	select BR2_PACKAGE_UTIL_LINUX_LIBUUID
>  	depends on BR2_TOOLCHAIN_HAS_THREADS
>  	depends on BR2_LARGEFILE # util-linux
> +	depends on BR2_USE_MMU # fork()

Please also update the dependencies comment.

baruch

>  	depends on BR2_USE_WCHAR # util-linux
>  	help
>  	  Rsyslog is a powerful and flexible syslog implementation
> -- 

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-05-14 18:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 18:28 [Buildroot] [PATCH 1/2] package/rsyslog: Add missing optional dependency libcrypt Bernd Kuhls
2014-05-14 18:28 ` [Buildroot] [PATCH 2/2] package/rsyslog: needs MMU (fork) Bernd Kuhls
2014-05-14 18:38   ` Baruch Siach [this message]
2014-05-14 18:57     ` Bernd Kuhls
2014-05-14 19:11       ` Yann E. MORIN
2014-05-14 19:37         ` Bernd Kuhls
2014-05-15 20:41 ` [Buildroot] [PATCH 1/2] package/rsyslog: Add missing optional dependency libcrypt Peter Korsgaard

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=20140514183816.GI4096@tarshish \
    --to=baruch@tkos.co.il \
    --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