All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Use libgudev as regular dependency
Date: Mon, 7 Dec 2015 14:57:50 +0000	[thread overview]
Message-ID: <56659E6E.2060704@imgtec.com> (raw)
In-Reply-To: <1449055626-4640-2-git-send-email-yegorslists@googlemail.com>

Dear Yegor Yefremov,

On 02/12/15 11:27, yegorslists at googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
> 
> Since eudev 3.1.3 libgudev is not shipped with this package,
> so libgudev can be used as regular dependency regardless of
> udev implementation selected.
> 
> Fixes following build error:
>   http://autobuild.buildroot.net/results/320/320c052bda0f1b5afb1e5c83a7fb4dca6227c5a1//
>   http://autobuild.buildroot.net/results/3b0/3b096f882030325b9290ad8860bd9cd373a11dc2//
> 
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Reviewed-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Tested-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>

Tested with this recent modem-manager autobuild failure:

http://autobuild.buildroot.net/results/373/3735baba46dee5bd846cc830e1e198ed783452c7/

Regards,

Vincent.

  parent reply	other threads:[~2015-12-07 14:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 11:27 [Buildroot] [PATCH 1/2] libgudev: remove systemd dependency yegorslists at googlemail.com
2015-12-02 11:27 ` [Buildroot] [PATCH 2/2] Use libgudev as regular dependency yegorslists at googlemail.com
2015-12-07 10:08   ` Yann E. MORIN
2015-12-07 14:57   ` Vicente Olivert Riera [this message]
2015-12-08 20:50   ` Peter Korsgaard
2015-12-07  9:41 ` [Buildroot] [PATCH 1/2] libgudev: remove systemd dependency Yann E. MORIN
2015-12-07 14:55 ` Vicente Olivert Riera
2015-12-08 20:47 ` Peter Korsgaard

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=56659E6E.2060704@imgtec.com \
    --to=vincent.riera@imgtec.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.