Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Junling Zheng <zhengjunling@huawei.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] uclibc: fix undefinition of '_dl_strchr' in libdl.a
Date: Fri, 3 Apr 2015 10:55:09 +0800	[thread overview]
Message-ID: <551E010D.8010309@huawei.com> (raw)
In-Reply-To: <0D1A6BA1-78E2-4AA5-9DD0-6553A974B447@gmail.com>

OK, I'll submit a patch v2 to both oe-core and uclibc upstream.

Cheers,

Junling

On 2015/4/2 22:35, Bernhard Reutner-Fischer wrote:
> On April 2, 2015 11:45:47 AM GMT+02:00, Junling Zheng <zhengjunling@huawei.com> wrote:
>> On 2015/4/2 14:42, Bernhard Reutner-Fischer wrote:
>>> On April 1, 2015 12:00:25 PM GMT+02:00, Junling Zheng
>> <zhengjunling@huawei.com> wrote:
>>>> The orign_path.patch introduced '_dl_strchr' into
>> ldso/ldso/dl-elf.c,
>>>
>>> Please fix the origin patch directly.
>>> Thanks,
>>>
>> Hi, Bernhard
>>
>> The orign_path.patch is backported from:
>>
>> http://lists.busybox.net/pipermail/uclibc/2011-March/045003.html
>>
>> It's an individual. Should I still fix this patch directly?
> 
> Yes.
>>
>> BTW, should uclibc upstream need this patch to avoid the above problem
>> too?
> 
> There currently is no in-tree user of these, so no.
> $ORIGIN support is on my todo list..
> 
>>
>> I had submitted a patch to the uclibc upstream, and expected your
>> review:)
> 
> See above :)
> 
> Cheers,
>>
>> Thanks,
>>
>> Junling
> 
> 
> 
> 




      reply	other threads:[~2015-04-03  2:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 10:00 [PATCH] uclibc: fix undefinition of '_dl_strchr' in libdl.a Junling Zheng
2015-04-02  6:34 ` Junling Zheng
2015-04-02  6:42 ` Bernhard Reutner-Fischer
2015-04-02  9:45   ` Junling Zheng
2015-04-02 14:35     ` Bernhard Reutner-Fischer
2015-04-03  2:55       ` Junling Zheng [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=551E010D.8010309@huawei.com \
    --to=zhengjunling@huawei.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rep.dot.nop@gmail.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