Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Maksim Kiselev <bigunclemax@gmail.com>
Cc: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 2/2] package/fio: add optional libiscsi dependency
Date: Sat, 29 Jul 2023 13:57:47 +0200	[thread overview]
Message-ID: <20230729135747.24539c4b@windsurf> (raw)
In-Reply-To: <20230516082340.1375834-2-bigunclemax@gmail.com>

On Tue, 16 May 2023 11:23:40 +0300
Maksim Kiselev <bigunclemax@gmail.com> wrote:

> Since commit 247ef2a fio has optional libiscsi engine support
> 
> This patch enables fio iscsi support if BR2_PACKAGE_LIBISCSI
> was selected

As pkg-config is used by the configure script to detect how to
compile/link against libiscsi, I've added host-pkgconf to the
dependencies when BR2_PACKAGE_LIBISCSI=y. I also updated a bit the
commit log to explain why we don't pass --disable-libiscsi.

Applied with those changes, thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-07-29 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  8:23 [Buildroot] [PATCH v1 1/2] package/fio: bump to version 3.34 Maksim Kiselev
2023-05-16  8:23 ` [Buildroot] [PATCH v1 2/2] package/fio: add optional libiscsi dependency Maksim Kiselev
2023-07-29 11:57   ` Thomas Petazzoni via buildroot [this message]
2023-07-29 11:57 ` [Buildroot] [PATCH v1 1/2] package/fio: bump to version 3.34 Thomas Petazzoni via buildroot

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=20230729135747.24539c4b@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bigunclemax@gmail.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=thomas.petazzoni@bootlin.com \
    /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