public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@mengyan1223.wang>
To: WENG Binyang <binyang.weng@forvia.com>,
	"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: How to enable GLIBCXX & CXXABI in yocto
Date: Wed, 27 Apr 2022 15:03:36 +0800	[thread overview]
Message-ID: <bf0ba3c46e1b12fce9d1da573a9ce7567083d8d6.camel@mengyan1223.wang> (raw)
In-Reply-To: <PR1P264MB3509D6C5852BBD80C38D588AF1FA9@PR1P264MB3509.FRAP264.PROD.OUTLOOK.COM>

On Wed, 2022-04-27 at 06:29 +0000, WENG Binyang wrote:
> Hi gcc-help team,
> 
> I am working on create a arm toolchain by yocto.
> I confirmed the generated toolchain, but found no GLIBCXX_3.* and
> CXXABI in libstdc++ for arm64. Please refer to the following.
> 
> xxx:~/Workspace/EMIRROR/sdk/linux/yocto-
> build/toolchain/sysroots/aarch64-linux/usr/lib$ strings
> libstdc++.so.6.0.28 | grep GLIBCXX
> GLIBCXX_FORCE_NEW
> GLIBCXX_DEBUG_MESSAGE_LENGTH
> 
> Could you tell me how to enable GLIBCXX_3* and CXXABI in yocto build? 

We do not know how GCC is configured during a yocto build.  You can
either provide more information (for example, attaching config.log of
libstdc++) or ask yocto:

https://www.yoctoproject.org/community/mailing-lists/

> Any unauthorized use or disclosure of this message is strictly
> prohibited.

This does not make sense posting to a public mailing list.  Please
disable such notices sending a mail to gcc-help.

-- 
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2022-04-27  7:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  6:29 WENG Binyang
2022-04-27  7:03 ` Xi Ruoyao [this message]
2022-04-27  9:26 ` Jonathan Wakely
2022-04-28  1:59   ` WENG Binyang

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=bf0ba3c46e1b12fce9d1da573a9ce7567083d8d6.camel@mengyan1223.wang \
    --to=xry111@mengyan1223.wang \
    --cc=binyang.weng@forvia.com \
    --cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).