From: Mike Looijmans <mike.looijmans@topic.nl>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: "libgudev" fails to build with current master
Date: Fri, 25 Sep 2015 07:18:24 +0200 [thread overview]
Message-ID: <5604D920.4030401@topic.nl> (raw)
In-Reply-To: <CALbNGRTopGO_K0BqpLaq27EeKhaC63QiE7Yo079PqOP5tQrSXA@mail.gmail.com>
On 24-09-15 18:45, Andreas Müller wrote:
> On Thu, Sep 24, 2015 at 3:40 PM, Mike Looijmans <mike.looijmans@topic.nl> wrote:
>> | checking for LIBUDEV... no
>> | configure: error: Package requirements (libudev >= 199) were not met:
>> |
>> | Requested 'libudev >= 199' but version of libudev is 182
>> |
>> ...
>>
>> ERROR: Task 5548
>> (/.../meta-oe/meta-oe/recipes-gnome/libgudev/libgudev_230.bb, do_configure)
>> failed with exit code '1'
>>
>>
> Which init system are you using - I guess not systemd
sysvinit (busybox).
I don't even use udev. But some packages think they depend on udev components,
so it's virtually impossible to not have udev being built.
I wonder how the init system would affect compilation of a package though.
M.
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
next prev parent reply other threads:[~2015-09-25 5:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 13:40 "libgudev" fails to build with current master Mike Looijmans
2015-09-24 16:45 ` Andreas Müller
2015-09-24 23:22 ` Andreas Müller
2015-09-25 6:11 ` Mike Looijmans
2015-09-25 6:32 ` Mike Looijmans
2015-09-25 6:25 ` Martin Jansa
2015-09-25 6:33 ` Andreas Müller
2015-09-25 5:18 ` Mike Looijmans [this message]
2015-09-25 6:28 ` Martin Jansa
2015-09-25 6:35 ` Mike Looijmans
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=5604D920.4030401@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-devel@lists.openembedded.org \
/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