From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: WARNING: QA Issue: udev: /lib/libgudev-1.0.so.0.0.1, installed in the base_prefix, requires a shared library under exec_prefix (/usr)
Date: Sat, 25 Aug 2012 17:48:47 +0100 [thread overview]
Message-ID: <503901EF.8050908@r-finger.com> (raw)
In-Reply-To: <CAK18fxFu6M11cia+C9EnJovtqFYnV4AaHzmoNZ1vJrRWMtLoUg@mail.gmail.com>
On 25/08/12 16:29, Andrei Gherzan wrote:
> The obvious fix would be to move libgudev in /usr but before
> doing this we need to be sure that nobody needs this in the early stages of
> booting.
That does not really matter; as things are if something is trying to use
libgudev before /usr is mounted, it will not work anyway, so moving it
under /usr/lib will not break anything that is not already broken per
se. But it could possibly break libgudev itself -- I think this is an
upstream bug that would be best pursued with the udev developers.
Tomas
prev parent reply other threads:[~2012-08-25 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 13:14 WARNING: QA Issue: udev: /lib/libgudev-1.0.so.0.0.1, installed in the base_prefix, requires a shared library under exec_prefix (/usr) Elvis Dowson
2012-08-25 15:29 ` Andrei Gherzan
2012-08-25 16:48 ` Tomas Frydrych [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=503901EF.8050908@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--cc=yocto@yoctoproject.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.