From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] xlib_libXpm: needs MMU (fork)
Date: Wed, 30 Apr 2014 00:54:19 +0200 [thread overview]
Message-ID: <20140430005419.6f1a456a@skate> (raw)
In-Reply-To: <20140429200722.GQ4531@tarshish>
Dear Baruch Siach,
On Tue, 29 Apr 2014 23:07:22 +0300, Baruch Siach wrote:
> This dependency should be propagated further recursively. Many packages select
> BR2_PACKAGE_XLIB_LIBXAW and all of them must also depend on BR2_USE_MMU.
Maybe we should take a step back and see if libXpm could be fixed to
not use fork() at all, or use vfork().
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-04-29 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 19:37 [Buildroot] [PATCH v2 1/1] xlib_libXpm: needs MMU (fork) Bernd Kuhls
2014-04-29 20:07 ` Baruch Siach
2014-04-29 22:54 ` 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=20140430005419.6f1a456a@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox