From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fio: new package
Date: Wed, 25 Dec 2013 17:32:53 -0300 [thread overview]
Message-ID: <20131225203252.GB7812@localhost> (raw)
In-Reply-To: <20131225212829.603981b9@skate>
On Wed, Dec 25, 2013 at 09:28:29PM +0100, Thomas Petazzoni wrote:
> Dear Ezequiel Garcia,
>
> On Wed, 25 Dec 2013 17:17:32 -0300, Ezequiel Garcia wrote:
>
> > > Thanks, I've applied this, after making several changes.
> > >
> >
> > All the changes look good to me, thanks for doing this and
> > sorry for being lazy and not take better care to push this
> > submission.
>
> We still have the problem that fio uses posix_madvise(), which isn't
> supported in uClibc 0.9.33. It is supported in uClibc git, and we have
> backported the patch in package/uclibc/, so Buildroot internal
> toolchains are working fine.
>
> But older uClibc toolchains do not work, and are causing build failures
> such as
> http://autobuild.buildroot.org/results/f7a/f7ae7ac2b5da9afc6314f1e813300597896e5ca6/build-end.log.
>
> I believe the best solution for now is to mark this package as not
> available for uClibc toolchains.
>
Right. And in parallel, we can also take care of upstreaming a patch which uses
HAVE_POSIX_MADVISE to handle such case.
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-25 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 15:22 [Buildroot] [PATCH] fio: new package Ezequiel Garcia
2013-12-25 16:34 ` Thomas Petazzoni
2013-12-25 20:17 ` Ezequiel Garcia
2013-12-25 20:28 ` Thomas Petazzoni
2013-12-25 20:32 ` Ezequiel Garcia [this message]
2013-12-26 9:40 ` Thomas Petazzoni
2013-12-26 11:30 ` Ezequiel Garcia
2013-12-26 13:38 ` Thomas Petazzoni
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=20131225203252.GB7812@localhost \
--to=ezequiel.garcia@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.