From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ipkg: needs MMU
Date: Tue, 26 Jul 2016 14:15:57 +0300 [thread overview]
Message-ID: <20160726111557.GY3588@tarshish> (raw)
In-Reply-To: <20160726100101.208d0299@free-electrons.com>
Hi Thomas,
On Tue, Jul 26, 2016 at 10:01:01AM +0200, Thomas Petazzoni wrote:
> On Tue, 26 Jul 2016 09:59:29 +0200, Thomas Petazzoni wrote:
> > 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.
>
> I was indeed a bit surprised to see this patch: we have been having
> Blackfin configurations for a long time in the autobuilders, and we
> never had to add a BR2_USE_MMU dependency on this package.
>
> So I believe there's something a bit more subtle going on here.
Right. It's this code from libbb/libbb.h:
/* Cope with mmu-less systems somewhat gracefully */
#if defined(__UCLIBC__) && !defined(__ARCH_HAS_MMU__)
#define fork vfork
#endif
This breaks musl that does not define __UCLIBC__. I posted an updated patch to
uses HAVE_FORK instead.
Is there anyone actually using this package anyway? Even its homepage is not
accessible here (handhelds.org does not resolve).
Thanks for reviewing,
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2016-07-26 11:15 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
2016-07-26 8:01 ` Thomas Petazzoni
2016-07-26 11:15 ` Baruch Siach [this message]
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=20160726111557.GY3588@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