From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] x264: needs mmu
Date: Mon, 2 May 2016 12:42:40 -0300 [thread overview]
Message-ID: <57277570.9060404@zacarias.com.ar> (raw)
In-Reply-To: <87eg9kqxmk.fsf@dell.be.48ers.dk>
On 02/05/16 12:37, Peter Korsgaard wrote:
> Ok - Thomas, do you know if madvise generally isn't available or if it
> is something specific to the binary bfin toolchain?
>
> I'll kick off a build with our new stm32f defconfig and look.
Ostensibly madvise() can be thrown away if the target doesn't support
it, though it would require submitting a bunch of patches upstream ;)
Regards.
next prev parent reply other threads:[~2016-05-02 15:42 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
2016-05-02 15:37 ` Peter Korsgaard
2016-05-02 15:42 ` Gustavo Zacarias [this message]
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=57277570.9060404@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox