From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] udisks: bump to version 1.0.5
Date: Wed, 2 Sep 2015 11:33:06 +0200 [thread overview]
Message-ID: <20150902113306.6cb82300@free-electrons.com> (raw)
In-Reply-To: <1441186284-61034-1-git-send-email-Vincent.Riera@imgtec.com>
Dear Vicente Olivert Riera,
On Wed, 2 Sep 2015 10:31:23 +0100, Vicente Olivert Riera wrote:
> This version depends on libgudev, otherwise it fails with an error like
> this one:
>
> checking for GUDEV... no
> configure: error: Package requirements (gudev-1.0 >= 147) were not met:
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> package/udisks/Config.in | 1 +
> package/udisks/udisks.hash | 2 +-
> package/udisks/udisks.mk | 5 +++--
> 3 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/package/udisks/Config.in b/package/udisks/Config.in
> index a5da2bf..8b8fd28 100644
> --- a/package/udisks/Config.in
> +++ b/package/udisks/Config.in
> @@ -12,6 +12,7 @@ config BR2_PACKAGE_UDISKS
> select BR2_PACKAGE_PARTED
> select BR2_PACKAGE_LVM2
> select BR2_PACKAGE_LIBATASMART
> + select BR2_PACKAGE_LIBGUDEV
No: libgudev should only be used when systemd is used. Otherwise, it's
provided by eudev.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-02 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 9:31 [Buildroot] [PATCH 1/2] udisks: bump to version 1.0.5 Vicente Olivert Riera
2015-09-02 9:31 ` [Buildroot] [PATCH 2/2] udisks: fix build with newer glibc versions Vicente Olivert Riera
2015-09-02 9:33 ` Thomas Petazzoni [this message]
2015-09-02 9:55 ` [Buildroot] [PATCH 1/2] udisks: bump to version 1.0.5 Vicente Olivert Riera
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=20150902113306.6cb82300@free-electrons.com \
--to=thomas.petazzoni@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