From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ipkg: needs MMU
Date: Tue, 26 Jul 2016 09:59:29 +0200 [thread overview]
Message-ID: <20160726095929.63583d2e@free-electrons.com> (raw)
In-Reply-To: <b8ef63602bd75ed7fe6b8d87d48e5d36680f3c91.1469505637.git.baruch@tkos.co.il>
Hello,
On Tue, 26 Jul 2016 07:00:37 +0300, Baruch Siach wrote:
> Fixes:
> http://autobuild.buildroot.net/results/6cf/6cf75e08795d9ab194ce4e882c0f4858bad979c3/
> http://autobuild.buildroot.net/results/964/964d8f694bc7d05b35411eabfbadf40bbf6337ae/
> http://autobuild.buildroot.net/results/0f2/0f2cddf89af3ad4330556acd04ab6cb080370e24/
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/ipkg/Config.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/ipkg/Config.in b/package/ipkg/Config.in
> index 4b2078d9cd70..d93e1d17b3dd 100644
> --- a/package/ipkg/Config.in
> +++ b/package/ipkg/Config.in
> @@ -1,5 +1,6 @@
> config BR2_PACKAGE_IPKG
> bool "ipkg"
> + depends on BR2_USE_MMU # fork()
I think this needs more investigation, because:
BR2_bfin=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_INIT_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_IPKG=y
# BR2_TARGET_ROOTFS_TAR is not set
which is a noMMU configuration, is able to build ipkg just fine.
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-26 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 4:00 [Buildroot] [PATCH] ipkg: needs MMU Baruch Siach
2016-07-26 7:59 ` Thomas Petazzoni [this message]
2016-07-26 8:01 ` Thomas Petazzoni
2016-07-26 11:15 ` Baruch Siach
2016-07-26 11:48 ` Thomas Petazzoni
2016-07-26 12:14 ` Baruch Siach
2016-07-26 12:52 ` Thomas Petazzoni
2016-07-26 15:08 ` Baruch Siach
2016-07-26 15:19 ` Thomas Petazzoni
2016-07-26 18:10 ` Khem Raj
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=20160726095929.63583d2e@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 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.