From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>,
yocto@yoctoproject.org
Subject: Re: Pyro's uninative and libstdc++ symbols
Date: Tue, 29 Aug 2017 09:03:28 +0100 [thread overview]
Message-ID: <1503993808.32591.312.camel@linuxfoundation.org> (raw)
In-Reply-To: <871snzdd5s.fsf@rkubodac-desk.ger.corp.intel.com>
On Fri, 2017-08-25 at 14:50 +0200, Raphael Kubo da Costa wrote:
> I've recently updated my host system to Fedora 26, which has GCC 7.
>
> This seems to be causing some issues on Pyro, where I have a -native
> recipe that is built with my system's g++ and ends up generating a
> binary with the following symbol:
>
> 0000000000000000 DF *UND* 0000000000000000 GLIBCXX_3.4.23
> std::basic_string<char, std::char_traits<char>, std::allocator<char>
> >::basic_string(std::string const&, unsigned long,
> std::allocator<char> const&)
>
> GLIBCXX_3.4.23 is not part of Pyro's uninative's libstdc++, so when
> that
> binary is invoked in another (non-native) recipe as part of
> do_configure
> it fails to run:
>
> gn: /data/src/yocto/poky/build/tmp/sysroots-uninative/x86_64-
> linux/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.23' not found
> (required by gn)
>
> Is there anything I should be doing differently here?
We need to update the uninative version in pyro to the more recent
version in master. uninative works on the principle that it the same
version or newer than the host system and for older releases this
ceases to be the case unless we upgrade it.
Cheers,
Richard
next prev parent reply other threads:[~2017-08-29 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 12:50 Pyro's uninative and libstdc++ symbols Raphael Kubo da Costa
2017-08-25 14:55 ` Chris Z.
2017-08-29 8:03 ` Richard Purdie [this message]
2017-09-01 19:14 ` akuster
2017-09-01 21:44 ` Richard Purdie
2017-09-07 14:28 ` Raphael Kubo da Costa
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=1503993808.32591.312.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=raphael.kubo.da.costa@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.