Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] acl: fix build problems with rpath on older libtool
Date: Fri, 18 Feb 2011 15:37:10 +0100	[thread overview]
Message-ID: <4D5E8416.2060908@eukrea.com> (raw)
In-Reply-To: <4D5E81F9.5060605@mentor.com>

Hi Tom,

On 18/02/2011 15:28, Tom Rini wrote:
> On 02/18/2011 04:32 AM, Eric Bénard wrote:
>> * bump INC_PR
>>
>> Signed-off-by: Eric Bénard<eric@eukrea.com>
>> ---
>> recipes/udev/acl_2.2.49.bb | 5 ++++-
>> 1 files changed, 4 insertions(+), 1 deletions(-)
>>
>> diff --git a/recipes/udev/acl_2.2.49.bb b/recipes/udev/acl_2.2.49.bb
>> index 5a37c57..20f94db 100644
>> --- a/recipes/udev/acl_2.2.49.bb
>> +++ b/recipes/udev/acl_2.2.49.bb
>> @@ -1,7 +1,7 @@
>> DESCRIPTION = "Commands for Manipulating POSIX Access Control Lists"
>> LICENSE = "GPLv2"
>>
>> -PR = "r3"
>> +PR = "r4"
>>
>> DEPENDS = "attr"
>>
>> @@ -20,6 +20,9 @@ EXTRA_OECONF = " --enable-gettext=yes \
>> do_configure_append() {
>> # gettext hack
>> echo "#define _(str) str">> ${S}/include/config.h
>> + # use same fix as libiconv
>> + sed -i -e s/^hardcode_libdir_flag_spec/#hardcode_libdir_flag_spec/ \
>> + -e s/^runpath_var/#runpath_var/ ${S}/*-libtool
>> }
>>
>> do_configure_prepend() {
>
> I've actually got something similar, but based on how poky fixed this queued
> up, and while I was in there I cleaned up the paths a bit too. But you got it
> posted first, so do you have a preference?
>
no problem, just push your patch with cleaned paths.

Eric



      reply	other threads:[~2011-02-18 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 11:32 [PATCH] acl: fix build problems with rpath on older libtool Eric Bénard
2011-02-18 14:28 ` Tom Rini
2011-02-18 14:37   ` Eric Bénard [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=4D5E8416.2060908@eukrea.com \
    --to=eric@eukrea.com \
    --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