From: "kai" <kai.kang@windriver.com>
To: "Jeremy A. Puhlman" <jpuhlman@mvista.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] buildtools-extended-tarball: add nativesdk-glibc
Date: Thu, 14 May 2020 15:36:58 +0800 [thread overview]
Message-ID: <4746673e-2ca8-379b-c02f-df3f90739fef@windriver.com> (raw)
In-Reply-To: <d8911cb6-0337-11c9-5bd9-950939299379@windriver.com>
On 2020/5/12 上午10:49, Kang Kai wrote:
> On 2020/5/12 上午10:47, Jeremy A. Puhlman wrote:
>>
>>
>> On 5/11/2020 7:30 PM, Kang Kai wrote:
>>> On 2020/5/10 下午9:40, Richard Purdie wrote:
>>>> On Wed, 2020-05-06 at 09:54 +0800, kai wrote:
>>>>> From: Kai Kang <kai.kang@windriver.com>
>>>>>
>>>>> It requires gcc 5.0 via OE-Core rev abc741a. On centos 7, the gcc
>>>>> version is too low then it has to build with buildtools-extended-
>>>>> tarball
>>>>> which provides nativesdk-gcc.
>>>>>
>>>>> But it fails to build nspr-native:
>>>>>
>>>>>> gcc abstract.o -Xlinker -L../../dist/lib -lplc4 -L../../dist/lib
>>>>>> -lnspr4 -lpthread -o abstract
>>>>>> /PATH/TO/x86_64-wrlinuxsdk-linux/bin/ld: /lib64/librt.so.1:
>>>>>> undefined reference to `__clock_getcpuclockid@GLIBC_PRIVATE'
>>>>>> /PATH/TO/x86_64-wrlinuxsdk-linux/bin/ld: /lib64/librt.so.1:
>>>>>> undefined reference to `__clock_nanosleep@GLIBC_PRIVATE'
>>>>>> /PATH/TO/x86_64-wrlinuxsdk-linux/bin/ld: /lib64/librt.so.1:
>>>>>> undefined reference to `__clock_settime@GLIBC_PRIVATE'
>>>>>> /PATH/TO/x86_64-wrlinuxsdk-linux/bin/ld: /lib64/librt.so.1:
>>>>>> undefined reference to `__clock_getres@GLIBC_PRIVATE'
>>>>>> collect2: error: ld returned 1 exit status
>>>>>> make: *** [Makefile:379: abstract] Error 1
>>>>> Add nativesdk-glibc to buildtools-extended-tarball. And it increases
>>>>> size of buildtools-extended-tarball about 3K from 48356989 to
>>>>> 48360329.
>>>>>
>>>>> Signed-off-by: Kai Kang <kai.kang@windriver.com>
>>>>> ---
>>>>> meta/recipes-core/meta/buildtools-extended-tarball.bb | 1 +
>>>>> 1 file changed, 1 insertion(+)
>>>> This doesn't make sense. Does it mean we need a new uninative version
>>>> instead?
>>>>
>>>> Cheers,
>>>>
>>>> Richard
>>>>
>>> ```This works in dunfell, as of right now. This should have been
>>> fixed with:
>>>
>>> ```https://patchwork.openembedded.org/patch/171584/
>>>
>>> Hi Jeremy,
>>>
>>> I can't receive mails from maillist for now. So reply here.
>>>
>>> I suppose when I build oe-core master on ubunu 16.04, it already
>>> contains the commit. I'll double check it.
>> Yeah it is in master right now. I am not entirely sure why you would
>> be seeing it. There was some discussion on
>> the list about twiddling with the location of /etc/ld.so.conf and
>> relocating it in the generation of sdks in general, but
>> I have not been able to poke at it today. If that went in, it might
>> have caused the issue. Basically what I saw when I was
>> looking in to it, was the sdk ld.so.conf was not getting loaded(in
>> the case of the patch because it was looking for etc/etc), but
>> if it got moved or something similar, it might cause a similar issue.
>>
>> If you are still seeing the issue on master, strace the link of the
>> file with -f and look at what is going on with the load of ld.so.conf
>> and
>> that might explain what is going on. Also make sure that ld.so.conf
>> is still there and has reasonable content.
>
>
> Thank you very much for your detailed comment. I'll try it.
Hi Richard & Jeremy,
I tried buildtools-extended-tarball with latest oe-core repo, and it
could build nspr-native on both ubuntu 16.04 and centos 7.7. Maybe it is
fixed along with recent update of buildtools-extend.
Thanks a lot for your replies.
Regards,
Kai
>
>
>>
>>
>
--
Kai Kang
Wind River Linux
prev parent reply other threads:[~2020-05-14 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 1:54 [PATCH] buildtools-extended-tarball: add nativesdk-glibc kai
2020-05-10 13:40 ` [OE-core] " Richard Purdie
2020-05-11 19:21 ` Jeremy Puhlman
2020-05-12 2:30 ` kai
2020-05-12 2:47 ` Jeremy Puhlman
2020-05-12 2:49 ` kai
2020-05-14 7:36 ` kai [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=4746673e-2ca8-379b-c02f-df3f90739fef@windriver.com \
--to=kai.kang@windriver.com \
--cc=jpuhlman@mvista.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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