From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: kai <kai.kang@windriver.com>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] buildtools-extended-tarball: add nativesdk-glibc
Date: Sun, 10 May 2020 14:40:55 +0100 [thread overview]
Message-ID: <080c0849554edd5710f68f6283a020f578968de9.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200506015447.13003-1-kai.kang@windriver.com>
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
next prev parent reply other threads:[~2020-05-10 13:40 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 ` Richard Purdie [this message]
2020-05-11 19:21 ` [OE-core] " 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
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=080c0849554edd5710f68f6283a020f578968de9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@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