On Tue, Oct 25, 2022 at 03:56 AM, Richard Purdie wrote:
>
> I'm a bit worried that we're seeing conflicting flags, it makes me
> wonder whether we have the right ones in our tune, or, are we mapping
> between RUST_HOST_SYS and HOST_SYS correctly.
>
> I'm guessing this is from "-mfpu=vfpv3-d16" a
On Mon, 2022-10-24 at 10:10 -0700, Anton Antonov wrote:
> Hi all,
>
> After this change (using RUST_HOST_SYS instead of
> HOST_SYS): https://github.com/yoctoproject/poky/commit/5c45b73c8fa445
> b5192bb9fac1bc80b038b44c0d builds of parsec-service recipe for
> qemuarm machine started to fail:
> c
And yes, seems like we'll have to set CRATE_CC_NO_DEFAULTS globally
and fix any issues that happen because of it.
Alex
On Mon, 24 Oct 2022 at 21:02, Alexander Kanavin via
lists.openembedded.org
wrote:
>
> On Mon, 24 Oct 2022 at 19:10, Anton Antonov wrote:
>
> > To fix the issue in our recipe
On Mon, 24 Oct 2022 at 19:10, Anton Antonov wrote:
> To fix the issue in our recipe we can define “CRATE_CC_NO_DEFAULTS” env
> variable which disables adding compiler flags in "cc-rs":
> https://github.com/rust-lang/cc-rs#external-configuration-via-environment-variables
> So, my questions is
Hi all,
After this change (using RUST_HOST_SYS instead of HOST_SYS):
https://github.com/yoctoproject/poky/commit/5c45b73c8fa445b5192bb9fac1bc80b038b44c0d
builds of parsec-service recipe for qemuarm machine started to fail:
cc1: error: switch '-mcpu=cortex-a15' conflicts with switch '-march=armv7
