From: yzhu1 <Yanjun.Zhu@windriver.com>
To: Khem Raj <raj.khem@gmail.com>,
"rongqing.li@windriver.com" <rongqing.li@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] relocate_sdk.py: fix lib path error
Date: Thu, 12 Jun 2014 18:14:46 +0800 [thread overview]
Message-ID: <53997D96.5040906@windriver.com> (raw)
In-Reply-To: <CAMKF1sp27ENENTNh6B0woVgh9AmY6zfpLX6Q19y1NciY8QUzKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2730 bytes --]
On 06/06/2014 08:22 PM, Khem Raj wrote:
>
>
> On Friday, June 6, 2014, <rongqing.li@windriver.com
> <mailto:rongqing.li@windriver.com>> wrote:
>
> From: yzhu1 <yanjun.zhu@windriver.com <javascript:;>>
>
> In centos 5.9 32bit, ld lib does not contain some flags, so ld
> lib is not parsed. So correct lib path is not got from ld lib.
>
>
> Can you explain with examples what's going on here ?
Hi,
Before relocate_sdk.sh is executed, it needs the parameters:
path/ld-linux-x86-64.so.2 path/dmesg.util-linux path/kill.util-linux
path/reset.util-linux .....
The file list (path/dmesg.util-linux path/kill.util-linux
path/reset.util-linux .....) is collected by "grep
'\(executable\|dynamically linked\)'".
So "dynamically linked" is very import to the file ld-linux-x86-64.so.2.
But in redhat 5.9(32 bit)
This file is as below:
ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped
In Ubuntu 12.04 (64bit)
This file is as below:
ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically
linked, BuildID[sha1]=0xbb8c5184d8d41f31093193a2ec8d3f6f10964cd2, stripped
In this case, we can find in Ubuntu 12.04(64 bit), the flag "dynamically
linked" is present, so ld-linux-x86-64.so.2 can be included in the file
list. relocate_sdk.py can work according to the information from
ld-linux-x86-64.so.2. But in redhat 5.9(32bit), the flag does not exist.
relocate_sdk.py can not get the information from ld-linux-x86-64.so.2
since this file is not included in the file list.
The same error occurs on redhat6.0(32 bit).
So the direct solution to this defect is to force this file
ld-linux-x86-64.so.2 exist in file list.
If any problem, please feel free to let me know.
Best Regards!
Zhu Yanjun
>
> Signed-off-by: yzhu1 <yanjun.zhu@windriver.com <javascript:;>>
> ---
> scripts/relocate_sdk.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/relocate_sdk.py b/scripts/relocate_sdk.py
> index 05d9fd6..a05a7fa 100755
> --- a/scripts/relocate_sdk.py
> +++ b/scripts/relocate_sdk.py
> @@ -201,7 +201,7 @@ else:
> new_prefix = sys.argv[1].encode()
> new_dl_path = sys.argv[2].encode()
>
> -executables_list = sys.argv[3:]
> +executables_list = sys.argv[2:]
>
> for e in executables_list:
> perms = os.stat(e)[stat.ST_MODE]
> --
> 1.7.10.4
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org <javascript:;>
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
[-- Attachment #2: Type: text/html, Size: 4712 bytes --]
next prev parent reply other threads:[~2014-06-12 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 7:17 [PATCH] relocate_sdk.py: fix lib path error rongqing.li
2014-06-06 12:22 ` Khem Raj
2014-06-12 10:14 ` yzhu1 [this message]
2014-06-12 12:07 ` Laurentiu Palcu
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=53997D96.5040906@windriver.com \
--to=yanjun.zhu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=rongqing.li@windriver.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