From: Robert Yang <liezhi.yang@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-perl] [PATCH] meta-perl: fix for eglibc-gconvs
Date: Thu, 11 Sep 2014 23:16:43 +0800 [thread overview]
Message-ID: <5411BCDB.7040500@windriver.com> (raw)
In-Reply-To: <2640190.uKkUWoK2di@peggleto-mobl5.ger.corp.intel.com>
On 09/11/2014 11:03 PM, Paul Eggleton wrote:
> Hi Robert,
>
> On Tuesday 09 September 2014 08:02:09 Robert Yang wrote:
>> There is no eglibc-gconvs now, but glibc-gconvs.
>>
>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> ---
>> .../recipes-perl/libnet/libnet-libidn-perl_0.12.bb | 4 ++--
>> .../recipes-perl/libtext/libtext-iconv-perl_1.7.bb | 2 +-
>> 2 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/meta-perl/recipes-perl/libnet/libnet-libidn-perl_0.12.bb
>> b/meta-perl/recipes-perl/libnet/libnet-libidn-perl_0.12.bb index
>> 42b213d..f896d11 100644
>> --- a/meta-perl/recipes-perl/libnet/libnet-libidn-perl_0.12.bb
>> +++ b/meta-perl/recipes-perl/libnet/libnet-libidn-perl_0.12.bb
>> @@ -8,9 +8,9 @@ SECTION = "libs"
>> LICENSE = "Artistic-1.0 | GPLv1+"
>> HOMEPAGE = "http://search.cpan.org/dist/Net-LibIDN/"
>> DEPENDS += "libidn"
>> -# We must need eglibc-gconvs to enable charset related functions,
>> +# We must need glibc-gconv to enable charset related functions,
>> # such as Net::LibIDN::idn_to_ascii().
>> -RDEPENDS_${PN} += "eglibc-gconvs"
>> +RDEPENDS_${PN} += "glibc-gconv"
>
> Ah, should that be glibc-gconvs?
Yes, I think so, sorry, I was confused by glibc-gconv and glibc-gconvs,
will send a V2 tomorrow.
// Robert
>
> Cheers,
> Paul
>
prev parent reply other threads:[~2014-09-11 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 15:02 [meta-perl] [PATCH] meta-perl: fix for eglibc-gconvs Robert Yang
2014-09-11 15:03 ` Paul Eggleton
2014-09-11 15:16 ` Robert Yang [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=5411BCDB.7040500@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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