All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: [RFC] Fix udev pulling in libvolume-id-dev
Date: Wed, 14 Jan 2009 23:41:18 -0800	[thread overview]
Message-ID: <20090115074118.GC7020@gmail.com> (raw)
In-Reply-To: <gkmmn6$pmf$1@ger.gmane.org>

On (15/01/09 07:56), Koen Kooi wrote:
> On 15-01-09 07:14, Denys Dmytriyenko wrote:
>
>> libvolume-id-dev does not provide the actual .so library, but it contains a
>> symlink in /usr/lib, which points to /lib/libvolume.so.0 (the host one!)
>> instead of ../../lib/ one...
>
> That's the intended behaviours, since installing the packages will have  
> it point to ${libdir}/libvolume.so.0 on your device. I'm not sure if we  
> want to patch every package to use relative symlinks.

We would use -dev packages on staged area normally to compile other apps
depending on a given packge if we do not fix the symlink I think it will
try to link to wrong library.


>
>> The first patch attached fixes this in udev and should be a no brainer. Unless
>> someone objects, I'll push it in in a day or two.
>>
>> Since I was debugging the code which actually does this shlib magic in
>> package.bbclass, I thought it might be useful to prevent this kind of issues
>> in the future by skipping symlinks while looking for SONAME/NEEDED in the
>> objdump - please see the second patch attached and provide feedback.
>
> The change to package.bbclass looks OK to me, if that gets applied we  
> can leave out the udev patch.
>
> regards,
>
> Koen
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  reply	other threads:[~2009-01-15  7:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15  6:14 [RFC] Fix udev pulling in libvolume-id-dev Denys Dmytriyenko
2009-01-15  6:56 ` Koen Kooi
2009-01-15  7:41   ` Khem Raj [this message]
2009-01-15 11:10     ` Koen Kooi
2009-01-15 18:53       ` Khem Raj
2009-01-15 18:57         ` Koen Kooi
2009-03-14  1:08           ` Denys Dmytriyenko
2009-01-15 19:20         ` Tom Rini
2009-01-15 19:41           ` Koen Kooi
2009-01-15 15:58   ` Denys Dmytriyenko
2009-01-15  7:37 ` Khem Raj
2009-01-15 15:51   ` Denys Dmytriyenko
2009-01-18  4:18     ` Denys Dmytriyenko
2009-01-19  0:56       ` Otavio Salvador

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=20090115074118.GC7020@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.