From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] x264: needs mmu
Date: Mon, 2 May 2016 12:26:49 -0300 [thread overview]
Message-ID: <572771B9.6080807@zacarias.com.ar> (raw)
In-Reply-To: <87inywqy9f.fsf@dell.be.48ers.dk>
On 02/05/16 12:23, Peter Korsgaard wrote:
> Hmm, is that really generally true? I don't quite see why you cannot
> have madvise() without mmu. Looking at uClibc-ng, the option enabling
> madvise support doesn't depend on MMU support.
I've based the rule on previous 80b9dfce, 5b309e1a and 8d446718
scenarios and didn't investigate myself.
Regards.
next prev parent reply other threads:[~2016-05-02 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 12:44 [Buildroot] [PATCH] x264: needs mmu Gustavo Zacarias
2016-05-02 15:23 ` Peter Korsgaard
2016-05-02 15:26 ` Gustavo Zacarias [this message]
2016-05-02 15:37 ` Peter Korsgaard
2016-05-02 15:42 ` Gustavo Zacarias
2016-05-02 19:45 ` Peter Korsgaard
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=572771B9.6080807@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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.