From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alex Roberts <arob109@gmail.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Trouble enabling vtable-verify for gcc-cross
Date: Wed, 27 Sep 2023 23:41:38 +0100 [thread overview]
Message-ID: <257d2db0bbb4f2b10814f068bfa32e3941ae95b2.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAPkENw-000rkwb1gBmgVTa1RarUe0yUOwXM_NiXQd7RJ3C53sg@mail.gmail.com>
On Wed, 2023-09-27 at 09:40 -0500, Alex Roberts wrote:
> Hello All,
>
> I'm having trouble getting gcc-cross-9.3.0 recipe to build libvtv. I
> have added “—enable-vtable-verify” to EXTRA_OECONF via a .bbappend.
> The vtable stubs are added to libstdc++ but libvtv itself is not
> compiled. This causes recipes compiling with -fstandard-verify to fail
> because libvtv doesn’t exist and cannot be linked in.
>
> Looking at the autoconf files and the resulting Makefile, libvtv
> should be getting configured and compiled with the recipe, but I can
> not determine why it is not.
>
> Does anyone have experience enabling vtable-verify to a cross-compiler
> toolchain?
If libvtv is a separate library (I've not looked), I suspect there are
tweaks needed to the gcc-runtime recipe to build it?
Cheers,
Richard
next prev parent reply other threads:[~2023-09-27 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 14:40 Trouble enabling vtable-verify for gcc-cross Alex Roberts
2023-09-27 22:41 ` Richard Purdie [this message]
2023-09-28 2:16 ` Alex Roberts
[not found] ` <1788EE639287C667.1970@lists.yoctoproject.org>
2023-09-28 19:55 ` [yocto] " Alex Roberts
[not found] ` <1789283578AF2335.9230@lists.yoctoproject.org>
2023-10-01 21:05 ` Alex Roberts
2023-10-01 21:23 ` Khem Raj
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=257d2db0bbb4f2b10814f068bfa32e3941ae95b2.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=arob109@gmail.com \
--cc=yocto@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox