All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ipkg: fix no MMU musl build
Date: Tue, 26 Jul 2016 13:48:46 +0200	[thread overview]
Message-ID: <20160726134846.1a859d30@free-electrons.com> (raw)
In-Reply-To: <8aa4f13e1f931315ebfe037e16c7e5761c6f97eb.1469531300.git.baruch@tkos.co.il>

Hello,

On Tue, 26 Jul 2016 14:08:20 +0300, Baruch Siach wrote:
> Current code uses vfork() instead of fork() only when __UCLIBC__ is defined.
> This breaks musl MMU-less build. Add a patch making direct use of HAVE_FORK
> that configure defines when fork() is detected.

See my previous reply: there is no platform in Buildroot that uses musl
on noMMU systems. The only noMMU architecture supported by musl is
SuperH as far as I know, so there is 0 chance that the ARM and m68k
noMMU failures are caused by musl related issues.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-07-26 11:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 11:08 [Buildroot] [PATCH] ipkg: fix no MMU musl build Baruch Siach
2016-07-26 11:48 ` Thomas Petazzoni [this message]

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=20160726134846.1a859d30@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.