All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8851] New: Make sure fio can compile with libaio support if it the package is installed
Date: Fri, 15 Apr 2016 01:56:37 +0000	[thread overview]
Message-ID: <bug-8851-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=8851

            Bug ID: 8851
           Summary: Make sure fio can compile with libaio support if it
                    the package is installed
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: ckhardin at exablox.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

if libaio is being used, then make fio depend on it so that it gets compiled
with aio support.

diff --git a/package/fio/fio.mk b/package/fio/fio.mk
index 08fef5f..384be2e 100644
--- a/package/fio/fio.mk
+++ b/package/fio/fio.mk
@@ -9,6 +9,10 @@ FIO_SITE = git://git.kernel.dk/fio.git
 FIO_LICENSE = GPLv2 + special obligations
 FIO_LICENSE_FILES = COPYING

+ifeq ($(BR2_PACKAGE_LIBAIO),y)
+FIO_DEPENDENCIES += libaio
+endif
+
 define FIO_CONFIGURE_CMDS
        (cd $(@D); ./configure --cc="$(TARGET_CC)"
--extra-cflags="$(TARGET_CFLAGS)")
 endef

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2016-04-15  1:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15  1:56 bugzilla at busybox.net [this message]
2016-04-15  7:32 ` [Buildroot] [Bug 8851] Make sure fio can compile with libaio support if it the package is installed bugzilla at busybox.net
2016-04-19 21:40 ` bugzilla at busybox.net

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=bug-8851-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.