Hi Richard,
I’ve tested your approach. It doesn’t work for whatever reason.
CRATE_CC_NO_DEFAULTS is empty exported for native recipes:
$ MACHINE=qemuarm bitbake rust-native -e |grep CRATE_CC_NO_DEFAULTS
# $CRATE_CC_NO_DEFAULTS [3 operations]
# [export] "${'1' if d.getVar('CRATE_CC_NO_DEFAULTS') == 'true' else '0'}"
export CRATE_CC_NO_DEFAULTS=""
# $CRATE_CC_NO_DEFAULTS:class-native
CRATE_CC_NO_DEFAULTS:class-native=""
I also tried:
CRATE_CC_NO_DEFAULTS[export] = "${@oe.utils.conditional('CRATE_CC_NO_DEFAULTS',
'', '0', '1', d)}"
with the same result – empty export.
Cheers,
Anton
From: Richard Purdie <[email protected]>
Date: Friday, 18 November 2022 at 15:10
To: Anton Antonov <[email protected]>,
[email protected]
<[email protected]>
Subject: Re: [OE-core] [langdale][master][PATCH] rust: Do not use default
compiler flags defined in CC crate
On Fri, 2022-11-18 at 14:42 +0000, Anton Antonov wrote:
> Rust crates build dependecy C libraries using "CC" crate.
> This crate adds some default compiler parameters depending on target arch.
> For some target archs these parameters conflict with the parameters defined
> by OE.
>
> Warnings/errors like this can be seen in the case:
>
> cc1: error: switch '-mcpu=cortex-a15' conflicts with switch
> '-march=armv7-a+fp' [-Werror]
>
> Lets use the OE parameters only by exporting CRATE_CC_NO_DEFAULTS.
> https://github.com/rust-lang/cc-rs#external-configuration-via-environment-variables
>
> This patch fixes https://bugzilla.yoctoproject.org/show_bug.cgi?id=14947
>
> Signed-off-by: Anton Antonov <[email protected]>
> ---
> meta/classes-recipe/rust-target-config.bbclass | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/meta/classes-recipe/rust-target-config.bbclass
> b/meta/classes-recipe/rust-target-config.bbclass
> index 2710b4325d..4135335043 100644
> --- a/meta/classes-recipe/rust-target-config.bbclass
> +++ b/meta/classes-recipe/rust-target-config.bbclass
> @@ -401,3 +401,21 @@ python do_rust_gen_targets () {
> addtask rust_gen_targets after do_patch before do_compile
> do_rust_gen_targets[dirs] += "${RUST_TARGETS_DIR}"
>
> +# For building C dependecies only use compiler parameters defined in OE-core
> +# and ignore the default parameters defined in the CC crate.
> +#
> https://github.com/rust-lang/cc-rs#external-configuration-via-environment-variables
> +# For rust native recipes we still rely on the CC crate parameters.
> +
> +CRATE_CC_NO_DEFAULTS:class-target ?= "true"
> +CRATE_CC_NO_DEFAULTS:class-nativesdk ?= "true"
> +CRATE_CC_NO_DEFAULTS:class-native ?= ""
> +
> +# The CC crate checks for CRATE_CC_NO_DEFAULTS existence not value.
> +# Even empty CRATE_CC_NO_DEFAULTS will be taken into account.
> +# So, don't export it if empty.
> +do_compile:prepend() {
> + if [ -n "${CRATE_CC_NO_DEFAULTS}" ]; then
> + export CRATE_CC_NO_DEFAULTS="${CRATE_CC_NO_DEFAULTS}"
> + bbnote "CRATE_CC_NO_DEFAULTS is exported"
> + fi
> +}
That looks like a good start. I wondered if this might work as a
slightly cleaner solution?:
CRATE_CC_NO_DEFAULTS = "true"
CRATE_CC_NO_DEFAULTS:class-native = ""
CRATE_CC_NO_DEFAULTS[export] = "${'1' if d.getVar('CRATE_CC_NO_DEFAULTS') ==
'true' else '0'}"
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#173476):
https://lists.openembedded.org/g/openembedded-core/message/173476
Mute This Topic: https://lists.openembedded.org/mt/95113030/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
