From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ipkg: needs MMU
Date: Tue, 26 Jul 2016 13:48:01 +0200 [thread overview]
Message-ID: <20160726134801.1d2eb91b@free-electrons.com> (raw)
In-Reply-To: <20160726111557.GY3588@tarshish>
Hello,
On Tue, 26 Jul 2016 14:15:57 +0300, Baruch Siach wrote:
> 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.
We don't use musl on any noMMU platform today, so this certainly cannot
explain failures like:
http://autobuild.buildroot.net/results/6cf/6cf75e08795d9ab194ce4e882c0f4858bad979c3/
(which was the first one mentioned in your commit log), since this
failure happens with uClibc.
Looking at http://autobuild.buildroot.net/?reason=ipkg-0.99.163, I see
(looking only at the failures since the beginning of 2016) :
* Numerous failures on ARM noMMU (uClibc)
* Two failures on m68k noMMU (uClibc)
* An old failure on i686 due to download issue
i.e, none of the failures are caused by a musl-related build.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-26 11:48 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
2016-07-26 11:48 ` Thomas Petazzoni [this message]
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=20160726134801.1d2eb91b@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.