From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [STABLE][PATCH] udev 124: fix the absolute soname link in libvolume for SDK
Date: Fri, 24 Apr 2009 13:39:08 -0400 [thread overview]
Message-ID: <20090424173908.GF28636@denix.org> (raw)
In-Reply-To: <gssg3a$rpo$1@ger.gmane.org>
On Fri, Apr 24, 2009 at 03:50:34PM +0200, Koen Kooi wrote:
> On 24-04-09 10:11, Denys Dmytriyenko wrote:
>>
>> Signed-off-by: Denys Dmytriyenko<denis@denix.org>
>
>
> Looks OK to me:
>
> Acked-by: Koen Kooi <koen@openembedded.org>
Do I need another ack?
>> ---
>> recipes/udev/udev-124/libvolume-id-soname.patch | 12 ++++++++++++
>> recipes/udev/udev_124.bb | 3 ++-
>> 2 files changed, 14 insertions(+), 1 deletions(-)
>> create mode 100644 recipes/udev/udev-124/libvolume-id-soname.patch
>>
>> diff --git a/recipes/udev/udev-124/libvolume-id-soname.patch
>> b/recipes/udev/udev-124/libvolume-id-soname.patch
>> new file mode 100644
>> index 0000000..56365a4
>> --- /dev/null
>> +++ b/recipes/udev/udev-124/libvolume-id-soname.patch
>> @@ -0,0 +1,12 @@
>> +diff -uNr udev-124-orig/extras/volume_id/lib/Makefile
>> udev-124/extras/volume_id/lib/Makefile
>> +--- udev-124-orig/extras/volume_id/lib/Makefile 2008-06-12
>> 01:24:30.000000000 -0400
>> ++++ udev-124/extras/volume_id/lib/Makefile 2009-01-14 23:32:42.000000000
>> -0500
>> +@@ -113,7 +113,7 @@
>> + ifeq ($(libdir),$(usrlibdir))
>> + ln -sf $(SHLIB) $(DESTDIR)$(usrlibdir)/libvolume_id.so
>> + else
>> +- ln -sf $(libdir)/$(SHLIB) $(DESTDIR)$(usrlibdir)/libvolume_id.so
>> ++ ln -sf ../..$(libdir)/$(SHLIB) $(DESTDIR)$(usrlibdir)/libvolume_id.so
>> + endif
>> + $(INSTALL) -d $(DESTDIR)$(usrlibdir)/pkgconfig
>> + $(INSTALL_DATA) libvolume_id.pc
>> $(DESTDIR)$(usrlibdir)/pkgconfig/libvolume_id.pc
>> diff --git a/recipes/udev/udev_124.bb b/recipes/udev/udev_124.bb
>> index 76edb2f..37dc3a7 100644
>> --- a/recipes/udev/udev_124.bb
>> +++ b/recipes/udev/udev_124.bb
>> @@ -2,13 +2,14 @@ DESCRIPTION = "udev is a daemon which dynamically
>> creates and removes device nod
>> /dev/, handles hotplug events and loads drivers at boot time. It
>> replaces \
>> the hotplug package and requires a kernel not older than 2.6.12."
>> RPROVIDES_${PN} = "hotplug"
>> -PR = "r14"
>> +PR = "r15"
>>
>> SRC_URI =
>> "http://kernel.org/pub/linux/utils/kernel/hotplug/udev-${PV}.tar.gz \
>> file://noasmlinkage.patch;patch=1 \
>> file://flags.patch;patch=1 \
>> file://vol_id_ld.patch;patch=1 \
>> file://udevtrigger_add_devname_filtering.patch;patch=1 \
>> + file://libvolume-id-soname.patch;patch=1 \
>> file://mount.blacklist \
>> file://run.rules \
>> "
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2009-04-24 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 8:11 [STABLE][PATCH] udev 124: fix the absolute soname link in libvolume for SDK Denys Dmytriyenko
2009-04-24 13:50 ` Koen Kooi
2009-04-24 17:39 ` Denys Dmytriyenko [this message]
2009-04-24 17:56 ` Koen Kooi
2009-04-24 18:13 ` Philip Balister
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=20090424173908.GF28636@denix.org \
--to=denis@denix.org \
--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