On Tue, Oct 25, 2022 at 03:56 AM, Richard Purdie wrote:<br />
<blockquote>I'm a bit worried that we're seeing conflicting flags, it makes me<br />wonder whether we have the right ones in our tune, or, are we mapping<br />between RUST_HOST_SYS and HOST_SYS correctly.<br /><br />I'm guessing this is from "-mfpu=vfpv3-d16" and that we choose a<br />different fpu option?<br /><br />If the difference really is something that rust simply made a different<br />choice on, we should set CRATE_CC_NO_DEFAULTS. rust-native is a bit<br />messy and whilst I would prefer we found out why the flags don't work,<br />I think setting the value for target and probably nativesdk might at<br />least be an improvement:<br /><br />CRATE_CC_NO_DEFAULTS:class-target = "X"<br />CRATE_CC_NO_DEFAULTS:class-nativesdk = "X"<br /><br />or we could just clear it for native:<br /><br />CRATE_CC_NO_DEFAULTS:class-native = ""</blockquote>
<p>with CRATE_CC_NO_DEFAULTS defined rustc_driver can't be built for rust-native with an error:</p>
<p>error: linking with `/data/shared/yocto/poky/build/tmp/work/x86_64-linux/rust-native/1.63.0-r0/wrapper/build-rust-ccld` failed: exit status: 1<br />&nbsp; = note: /data/shared/yocto/poky/build/tmp/hosttools/ld: /data/shared/yocto/poky/build/tmp/work/x86_64-linux/rust-native/1.63.0-r0/rustc-1.63.0-src/build/x86_64-unknown-linux-gnu/stage0-rustc/x86_64-unknown-linux-gnu/release/deps/librustc_llvm-c2bba4d8034ef27f.rlib(RustWrapper.o): relocation R_X86_64_TPOFF32 against `_ZL9LastError' can not be used when making a shared object; recompile with -fPIC<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; collect2: error: ld returned 1 exit status</p>
<p>with</p>
<p>CRATE_CC_NO_DEFAULTS:class-target = "true"<br />CRATE_CC_NO_DEFAULTS:class-nativesdk = "true"</p>
<p>in rust-target-config.bbclass I can successively build native and target recipes.</p>
<p>I've raised an issue to follow this discussion:</p>
<p>https://bugzilla.yoctoproject.org/show_bug.cgi?id=14947</p>
<p>&nbsp;</p>
<p>Cheers,</p>
<p>Anton</p>