From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: New kmod {libdir} breaks udev, systemd build
Date: Tue, 15 May 2012 11:27:57 +0200 [thread overview]
Message-ID: <jot7j3$df9$1@dough.gmane.org> (raw)
In-Reply-To: <CAF6bG8fEnVNtkEO9iHtrpB822w-SNWzTd-4WSTr_SgNqNpHTtg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 14-05-12 19:42, Marko Lindqvist schreef:
> On 14 May 2012 20:23, Thilo Fromm <fromm@dresearch-fe.de> wrote:
>>
>> openembedded-core only features udev-164 (vs. -182 in meta-oe). -164 in
>> oe-core does not use libkmod, so there's no issue with libkmod in
>> oe-core. It's no surprise that it "worked for you", you were building
>> anicent tools.
>
> I know. I were asking why versions are setup like this. If -182 makes
> more sensible default, why it's not one in -core. My main point was that
> seemingly unrelated change to build xterm to my image (requiring meta-oe
> layer) caused *default* udev version to change (I'm not setting
> PREFERRED_VERSION anywhere).
Setting preferred versions is the task of the DISTRO. If the DISTRO doesn't
care about the udev version, it will change if you add different versions to
your stack. If that offends you, switch to another DISTRO.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJPsiGdAAoJEHZqAkdh1vT6qUIP/2l+gdBLEmcr1eNJAXa2brKf
7EpMMNChKurwoBQHJqWUFYWGfFDpTsda02jIV3sB4dZ7DzVCrs4MQrBQYBNvoYhb
/xrjnObNDv12mlVTmBU8mfL9BtkCGdjhEs9lq1WDGO6nTEVnlE3T8+skmoGuDfwV
vq1HejuwMNsM5SaC8/jEHDM41YT5gqDMOViSZhwIfSvCPzJ2dc4An5yq601HEIH4
T+SM+BpGLmUgsW0mMnTXgo61BCHc3DMtV3qVl8V/FJRm92OigWUFWihSE+lv9G6O
URpErYOwYFaQaqZs3Ma3MpBQ3GGj1q2FC0ypJ9PsdU2W4SPZsMxJD7VDg/1HbLzn
tsVQPB2+DILoIjUliq+YAAVERj0rAaGbHw6dvFKuaielYjBkCutj3UICG8i0tTyJ
rtIvK7NbWm9BON3t4EHpuzsmyQ90q24glbKGYsEF1F2ckaXj4TRntDcJPu9Cha/7
OQ3lunZINzRf2xKE/ixzmMvTlhehvhrusuV3QboRg0UBVAFlscjeTuZCf+VpX4SY
GKPEV9GZH/0aZwwQgx3/E/+tcwac+IKc+RGk6b3jU269Dz/ShcHmXsBWlCpw2St7
fNakj0PELguutLMqeEYTJedqUBFpfd6y7oz1upxyMF21EUkBdK9mvEF1OX9XmXhs
tQR8lTJjm8PJZ8doKJjk
=bXQJ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-05-15 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 12:48 New kmod {libdir} breaks udev, systemd build Thilo Fromm
2012-05-14 16:51 ` Marko Lindqvist
2012-05-14 17:23 ` Thilo Fromm
2012-05-14 17:42 ` Marko Lindqvist
2012-05-15 8:36 ` Thilo Fromm
2012-05-15 9:27 ` Koen Kooi [this message]
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='jot7j3$df9$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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 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.