Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fio: new package
Date: Thu, 26 Dec 2013 08:30:07 -0300	[thread overview]
Message-ID: <20131226113006.GA24120@localhost> (raw)
In-Reply-To: <20131226104037.6cb81f36@skate>

On Thu, Dec 26, 2013 at 10:40:37AM +0100, Thomas Petazzoni wrote:
> Dear Ezequiel Garcia,
> 
> On Wed, 25 Dec 2013 17:32:53 -0300, Ezequiel Garcia wrote:
> 
> > > 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.
> 
> The problem is what should we use in replacement of posix_madvise()
> when it is not available.
> 

madvise()?

If you do:

  #define posix_madvise madvise

then I've managed to fix the build issues on uClibc v0.9.32.

Problem is, I'm not sure there's a clean way to detect posix_madvise /
madvise presence; it must be done by hand in the configure script.

Anyway, it all sounds like too much work to fix such a small use case.
-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  reply	other threads:[~2013-12-26 11:30 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
2013-12-26  9:40         ` Thomas Petazzoni
2013-12-26 11:30           ` Ezequiel Garcia [this message]
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=20131226113006.GA24120@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox