Re: [yocto] [meta-tensorflow][PATCH] layer.conf: revert -> add dl layer to LAYERRECOMMENDS

[Randy MacLeod via lists.yoctoproject.org]

Add WR email and ping.
See also:
https://lists.yoctoproject.org/g/yocto/message/61918

Thanks,
../Randy

On 2023-12-15 1:35 p.m., Randy MacLeod via lists.yoctoproject.org wrote:

From: Randy MacLeod

The -dl (download) layers are not used anywhere but in Wind River products
so drop the line that was added in:
5044996 layer.conf: add dl layer to LAYERRECOMMENDS

Signed-off-by: Randy MacLeod
---
  conf/layer.conf | 2 --
  1 file changed, 2 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index ccb6343..60cbd52 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -21,6 +21,4 @@ LAYERDEPENDS_meta-tensorflow = " \
  
  LAYER_PATH_meta-tensorflow = "${LAYERDIR}"
  
-LAYERRECOMMENDS_meta-tensorflow += "meta-tensorflow-dl (= 4.1)"

-
  NON_MULTILIB_RECIPES:append = " tensorflow tensorflow-lite"





--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62091): https://lists.yoctoproject.org/g/yocto/message/62091
Mute This Topic: https://lists.yoctoproject.org/mt/103196189/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Nondeterministic errors with bitbake

[Randy MacLeod via lists.yoctoproject.org]

On 2024-01-02 4:49 p.m., daniele.lugli via lists.yoctoproject.org wrote:

Hi all and best wishes for the new year.

I recently worked with nanbield on Ubuntu 22.04.3 in a VirtualBox 
machine.
I added layers meta-intel and meta-realtime and, with a couple of 
small modifications to core-image-rt-extended.bb and to rt-app.bb, as 
suggested by some kind reader (see 
https://lists.yoctoproject.org/g/yocto/topic/103135158), and after a 
couple of restarts, I could obtain the image, prepare a .vdi from the 
.wic and boot a virtual machine with that disk.


Now I moved to a physical machine with Ubuntu 22.04.3. Here is the 
build configuration:


BB_VERSION   = "2.6.1"
BUILD_SYS    = "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "genericx86-64"
DISTRO   = "poky"
DISTRO_VERSION   = 
"4.3+snapshot-b92406d2313234dccd77b05fe74c09ba9617a738"

TUNE_FEATURES    = "m64 core2"
TARGET_FPU   = ""
meta
meta-poky
meta-yocto-bsp   = "master:b92406d2313234dccd77b05fe74c09ba9617a738"
meta-oe  = "master:10f1890af03dbb804bffd4fa7eda7729e08f12cb"
meta-intel   = "master:5cfefd9a8ff1f5a3534c1ba9d7d7f6971ed5d56f"
meta-realtime    = "master:489e1d6b34e46f845a4bfe6461a39c6a4bcb7794"

I am using exactly the same configuration as in the virtual Ubuntu and 
I have also applied the suggested modifications to 
core-image-rt-extended.bb and to rt-app.bb. So the situation should be 
the same.


I cannot understand why I am getting error messages which look random: 
when, after the error, I rerun bitbake, I get a different error.


As an instance, in the first run of bitbake core-image-extended.bb I get:

| 
/home/daniele/poky/build/tmp/work/x86_64-linux/cmake-native/3.27.7/cmake-3.27.7/Source/cmComputeComponentGraph.cxx:139:1: 
internal compiler error: Segmentation fault

|   139 | }
|   | ^
| 0x7fc36ca4251f ???
| ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
| 0x7fc36ca29d8f __libc_start_call_main
| ../sysdeps/nptl/libc_start_call_main.h:58
| 0x7fc36ca29e3f __libc_start_main_impl
|     ../csu/libc-start.c:392
| Please submit a full bug report,
| with preprocessed source if appropriate.
...
Summary: 1 task failed:
/home/daniele/poky/meta/recipes-devtools/cmake/cmake-native_3.27.7.bb:do_compile

Second attempt, without any modification. I get a different error:

ERROR: Task 
(virtual:native:/home/daniele/poky/meta/recipes-devtools/python/python3_3.11.5.bb:do_install) 
failed with exit code '139'
NOTE: Tasks Summary: Attempted 3568 tasks of which 3518 didn't need to 
be rerun and 1 failed.


Summary: 1 task failed:
virtual:native:/home/daniele/poky/meta/recipes-devtools/python/python3_3.11.5.

Third attempt, always without modifications. Still different:

| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
ERROR: Task 
(/home/daniele/poky/meta/recipes-devtools/gcc/gcc_13.2.bb:do_compile) 
failed with exit code '1'
NOTE: Tasks Summary: Attempted 6049 tasks of which 3567 didn't need to 
be rerun and 1 failed.


Summary: 1 task failed:
/home/daniele/poky/meta/recipes-devtools/gcc/gcc_13.2.bb:do_compile
Summary: There were 2 ERROR messages, returning a non-zero exit code.

And so on. Fourth attempt:

ERROR: Task 
(/home/daniele/poky/meta-realtime/recipes-extended/images/core-image-rt-extended.bb:do_rootfs) 
failed with exit code '1'
NOTE: Tasks Summary: Attempted 6700 tasks of which 6052 didn't need to 
be rerun and 1 failed.


Summary: 1 task failed:
/home/daniele/poky/meta-realtime/recipes-extended/images/core-image-rt-extended.bb:do_rootfs
Summary: There was 1 ERROR message, returning a non-zero exit code.

How is this possible? Problems in the communication with the server, 
or what?


I doubt it.  Did you look in the system logs?

I'd guess that the memory sub-system on your bare-metal ubu-22.04.3 
machine is bad.


Try another machine with exactly the same software if you can.

To test the memory on the original machine, you can try use memtest86+ 
as noted here:

https://askubuntu.com/questions/343114/how-to-check-for-errors-in-ram-via-ubuntu


If there's no indication that the memory is bad, do the problems also 
happen with the an older, more widely tested branch like kirkstone ?



../Randy




Thank you in advance and best regards

--
Daniele Lugli
General Logic srl
Viale Curreno, 41
10133 Torino
Italy
tel +39 329 3933041
www.general-logic.com 
www.linkedin.com/in/daniele-lugli 







--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62073): https://lists.yoctoproject.org/g/yocto/message/62073
Mute This Topic: https://lists.yoctoproject.org/mt/103491090/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]

[yocto] [meta-tensorflow] Layer should not contain a directory with another layer.

[Randy MacLeod via lists.yoctoproject.org]

Hongxu,

Tim Orling was pointing out that we had the -dl line that I just sent a 
fix for in meta-tensorflow.


He was also asking about the meta-demo layer without the meta-tensorflow 
layer.
I suspect that the layer index code can't and should be asked to handle 
that arrangement.


Nested layers are not allow.

Can you:

1. move all but the meta-demo dir into a new meta-tf directory
    to parallel meta-openembedded containing meta-oe

or
    just remove meta-demo?

2. update the README appropriately

3. Notify people that this change has happened.

4. Fix up released branches as needed.

5. Fix the yp list address: yo...@yoctoproject.org  -> 
yocto@lists.yoctoproject.org


❯ rg "yocto@yocto"
MAINTAINERS.md
17:list: yo...@yoctoproject.org"
23:git send-email -1 -M --to yo...@yoctoproject.org 
--subject-prefix=meta-tensorflow][PATCH


Thanks,

--

# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61918): https://lists.yoctoproject.org/g/yocto/message/61918
Mute This Topic: https://lists.yoctoproject.org/mt/103196224/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-tensorflow][PATCH] layer.conf: revert -> add dl layer to LAYERRECOMMENDS

[Randy MacLeod via lists.yoctoproject.org]

From: Randy MacLeod 

The -dl (download) layers are not used anywhere but in Wind River products
so drop the line that was added in:
   5044996 layer.conf: add dl layer to LAYERRECOMMENDS

Signed-off-by: Randy MacLeod 
---
 conf/layer.conf | 2 --
 1 file changed, 2 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index ccb6343..60cbd52 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -21,6 +21,4 @@ LAYERDEPENDS_meta-tensorflow = " \
 
 LAYER_PATH_meta-tensorflow = "${LAYERDIR}"
 
-LAYERRECOMMENDS_meta-tensorflow += "meta-tensorflow-dl (= 4.1)"
-
 NON_MULTILIB_RECIPES:append = " tensorflow tensorflow-lite"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61917): https://lists.yoctoproject.org/g/yocto/message/61917
Mute This Topic: https://lists.yoctoproject.org/mt/103196189/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Mold linker

[Randy MacLeod via lists.yoctoproject.org]

On 2023-02-15 2:22 a.m., Khem Raj via lists.yoctoproject.org wrote:

On Tue, Feb 14, 2023 at 9:36 PM Joel Winarske  wrote:

Has anyone played around with the mold linker?

https://github.com/rui314/mold


Curious what the build time difference might be on a large multi-core machine.

Yes, lightly. I found it similar to lld in many cases, only used it on
native links for chromium
it seems to be better at parallelization.


Has anyone checked recently, there's been quite a bit of work since Feb 
2023 (1)


Narpat might try this out for Chromium.

I'd expect that the overall build time isn't reduced much even on our 
100+ core systems
since there are just soo many .cpp files to compile but it's worth 
checking.


../Randy


1)

mold.git on main
❯ TZ=$(date +%z) git log --reverse --date-order --format="%cd" 
--date=iso-local 9615b8b962edc659f7113029c5c85a81b173e4dc... \

    | cut -d- -f1-2 \
    | uniq -c \
    | column -t \
    | perl -pwe 's{\s+}{\t}'
145    2023-01
34    2023-02
37    2023-03
11    2023-04
12    2023-06
55    2023-07
143    2023-08
43    2023-09
105    2023-10
95    2023-11
12    2023-12




Joel








--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61807): https://lists.yoctoproject.org/g/yocto/message/61807
Mute This Topic: https://lists.yoctoproject.org/mt/9693/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [yocto-autobuilder-helper][PATCH] config.json: temporarily disable pressure regulation for master-next ONLY

[Randy MacLeod via lists.yoctoproject.org]

From: Randy MacLeod 

Builds and oe-selftest runs have been seen to take around 16 hours.
Temporarily disable pressure regulation in master-next ONLY
to see if the pressure regulation is a significant part of what's
causing the slow down.

Signed-off-by: Randy MacLeod 
---
 config.json | 2 --
 1 file changed, 2 deletions(-)

diff --git a/config.json b/config.json
index 0c581d1..ffe216b 100644
--- a/config.json
+++ b/config.json
@@ -50,8 +50,6 @@
 "BB_NUMBER_THREADS = '16'",
 "BB_NUMBER_PARSE_THREADS = '16'",
 "PARALLEL_MAKE = '-j 16 -l 52'",
-"BB_PRESSURE_MAX_CPU = '1'",
-"BB_PRESSURE_MAX_IO = '1'",
 "XZ_MEMLIMIT = '5%'",
 "XZ_THREADS = '8'",
 "ZSTD_THREADS = '8'",
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61683): https://lists.yoctoproject.org/g/yocto/message/61683
Mute This Topic: https://lists.yoctoproject.org/mt/102587267/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Minutes: Yocto Project Weekly Triage Meeting 29/06/2023

[Randy MacLeod via lists.yoctoproject.org]

On 2023-06-29 11:14, Sakib Sajal wrote:


*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage

*Attendees: *Richard Purdie, Steve Sakoman, Stephen Jolley, Bruce 
Ashfield, Joshua Watt, Ross Burton, Trevor Gamblin, Randy Macleod, 
Alexandre Belloni, Tim Orling, Michael Opdenacker, Ryan Eatmon, Luca 
Ceresoli, Yoann Congal


*ARs:**
*

*Notes:
*
*
*

*Medium+ 4.3 Unassigned Enhancements/Bugs: *74 (Last week 73)

*Medium+ 4.99 Unassigned Enhancements/Bugs: *45**(Last week 44)

*AB Bugs: *68 (Last week 66) 


I bumped all the unassigned eSDK issues in:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Future_.26_4.99_Milestones

and fixed the titles so that they ALL consistently use the "eSDK:" 
prefix since that's clearly important! ;-)


--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60480): https://lists.yoctoproject.org/g/yocto/message/60480
Mute This Topic: https://lists.yoctoproject.org/mt/99852761/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Minutes: Yocto Project Weekly Triage Meeting 08/06/2023

[Randy MacLeod via lists.yoctoproject.org]

On 2023-06-08 11:29, Sakib Sajal wrote:


*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage

*Attendees: *Richard Purdie, Steve Sakoman, Stephen Jolley, Bruce 
Ashfield, Joshua Watt, Ross Burton, Trevor Gamblin, Randy Macleod, 
Alexandre Belloni, Tim Orling, Thomas Roos, Yoann Congal, Michael 
Opdenacker, Ryan Eatmon


*ARs:**
*

- Randy: Move bugs from M1 to M2 for autobuilder intermittent issues.

Actually: Move *unassigned* bugs from M1 to M2 for autobuilder 
intermittent issues.


Done.

../Randy


*Notes:
*
*
*

*Medium+ 4.3 Unassigned Enhancements/Bugs: *73 (Last week 72)

*Medium+ 4.99 Unassigned Enhancements/Bugs: *44**(Last week 44)

*AB Bugs: *74 (Last week 70) 



--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60310): https://lists.yoctoproject.org/g/yocto/message/60310
Mute This Topic: https://lists.yoctoproject.org/mt/99409361/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Minutes: Yocto Project Weekly Triage Meeting 25/05/2023

[Randy MacLeod via lists.yoctoproject.org]

On 2023-05-25 11:31, Sakib Sajal wrote:


*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage

*Attendees: *Richard Purdie, Steve Sakoman, Stephen Jolley, Ross 
Burton, Joshua Watt, Trevor Gamblin, Randy Macleod, Alexandre Belloni, 
Tim Orling, Thomas Roos, Yoann Congal, Michael Opdenacker, Pavel 
Zhukov, Jan & Sam


*ARs:**
*



*1. AlexB: *Alexandre Belloni teaches Yocto to new users and he tells 
then that the simply have to memorize which key variables are space 
separated; Alex is going to create a defect to get this list documented.


2. Sakib to drop Zheng Qiu from this list.

../Randy


**

*Notes:
*
*
*

*Medium+ 4.3 Unassigned Enhancements/Bugs: *72 (Last week 72)

*Medium+ 4.99 Unassigned Enhancements/Bugs: *44**(Last week 44)

*AB Bugs: *72 (Last week 72) 



--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60124): https://lists.yoctoproject.org/g/yocto/message/60124
Mute This Topic: https://lists.yoctoproject.org/mt/99132444/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-xilinx][PATCH] Use new variable LICENSE_FLAGS_ACCEPTED

[Randy MacLeod via lists.yoctoproject.org]

On 2023-04-22 22:49, Yu, Mingli wrote:

Ping.

Thanks,


Mingli,

Please re-send to:
meta-xil...@lists.yoctoproject.org
unless someone picks up the change and merges it before your morning.

See:
https://lists.yoctoproject.org/g/meta-xilinx

../Randy




On 4/24/22 11:20, Yu, Mingli wrote:

From: Mingli Yu 

Signed-off-by: Mingli Yu 
---
  meta-xilinx-bsp/README.md   | 4 ++--
  meta-xilinx-core/README.md  | 4 ++--
  meta-xilinx-core/README.qemu.md | 4 ++--
  3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta-xilinx-bsp/README.md b/meta-xilinx-bsp/README.md
index e4142861..85a5b38f 100644
--- a/meta-xilinx-bsp/README.md
+++ b/meta-xilinx-bsp/README.md
@@ -73,11 +73,11 @@ In order to use recipes that rely on restricted 
content the `xilinx` license
  flag must be white-listed in the build configuration (e.g. 
`local.conf`). This

  can be done on a per package basis:
  -    LICENSE_FLAGS_WHITELIST += "xilinx_pmu-rom"
+    LICENSE_FLAGS_ACCEPTED += "xilinx_pmu-rom"
    or generally:
  -    LICENSE_FLAGS_WHITELIST += "xilinx"
+    LICENSE_FLAGS_ACCEPTED += "xilinx"
    Generally speaking Xilinx content that is provided as a 
restricted download
  cannot be obtained without a Xilinx account, in order to use this 
content you

diff --git a/meta-xilinx-core/README.md b/meta-xilinx-core/README.md
index 8997760c..3fae999f 100644
--- a/meta-xilinx-core/README.md
+++ b/meta-xilinx-core/README.md
@@ -72,11 +72,11 @@ In order to use recipes that rely on restricted 
content the `xilinx` license
  flag must be white-listed in the build configuration (e.g. 
`local.conf`). This

  can be done on a per package basis:
  -    LICENSE_FLAGS_WHITELIST += "xilinx_pmu-rom-native"
+    LICENSE_FLAGS_ACCEPTED += "xilinx_pmu-rom-native"
    or generally:
  -    LICENSE_FLAGS_WHITELIST += "xilinx"
+    LICENSE_FLAGS_ACCEPTED += "xilinx"
    Generally speaking Xilinx content that is provided as a 
restricted download
  cannot be obtained without a Xilinx account, in order to use this 
content you
diff --git a/meta-xilinx-core/README.qemu.md 
b/meta-xilinx-core/README.qemu.md

index d0040b09..5cc599a4 100644
--- a/meta-xilinx-core/README.qemu.md
+++ b/meta-xilinx-core/README.qemu.md
@@ -10,11 +10,11 @@ The PMU ROM is available for download, and a 
specific recipe has been created

  to make this available: pmu-rom-native.
    The license on the software is Xilinx proprietary, so you may be 
required to

-enable the approprate LICENSE_FLAGS_WHITELIST to trigger the download.
+enable the approprate LICENSE_FLAGS_ACCEPTED to trigger the download.
  The license itself is available within the download at the URL 
referred to in

meta-xilinx-core/recipes-bsp/pmu-firmware/pmu-rom-native_2022.1.bb.
    Add the following to your local.conf to acknowledge you accept 
the proprietary

  xilinx license.
  -   LICENSE_FLAGS_WHITELIST:append = " xilinx"
+   LICENSE_FLAGS_ACCEPTED:append = " xilinx"







--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60101): https://lists.yoctoproject.org/g/yocto/message/60101
Mute This Topic: https://lists.yoctoproject.org/mt/98444684/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Install complete Rust and toolchans for image? #rust #yocto #sdk

[Randy MacLeod via lists.yoctoproject.org]

On 2023-04-30 19:01, Livius via lists.yoctoproject.org wrote:

Hi,


Hi,

I'm a bit late but here is some of what you were looking for:




What recipes should I use in IMAGE_INSTALL to install all of Rust
https://git.openembedded.org/openembedded-core/commit/?id=bb781f452299cfa6ec7fffd215b0af3149178f32 




and toolchains things for it on my target ARM board?

That's not a very specific question but there is:

meta/recipes-core/packagegroups/packagegroup-self-hosted.bb

Rust is not in that list yet and I suspect most people are not ready to 
add it either.

Once (if?) the kernel requires Rust, then we'll cha


What Yocto release was started to support Rust?


Started in  honister:

❯ git log --reverse --oneline  --grep  rust: | head -1
61e1570c6a rust: initial merge of most of meta-rust

poky.git on master-next [$]
❯ git branch -a --contains 61e1570c6a
  honister
  kirkstone
  kirkstone-next
  langdale
  master
* master-next
  mickledore

but there were significant improvements in Aug 2022 and later,
specifically the ability to put the rust toolchain on the target MACHINE.



Is ti possbile a make an SDK image with a Rust cross compiler like it is 
possible with GCC via mingw for Windows 10?


Likely but I'm not aware of anyone having done that.

Please let us know if you try it and if it works.
If it's important to you, a test case might be useful.

../Randy








--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59956): https://lists.yoctoproject.org/g/yocto/message/59956
Mute This Topic: https://lists.yoctoproject.org/mt/98604334/21656
Mute #rust:https://lists.yoctoproject.org/g/yocto/mutehashtag/rust
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #sdk:https://lists.yoctoproject.org/g/yocto/mutehashtag/sdk
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [kirkstone] `rustc` executable missing from sdk

[Randy MacLeod via lists.yoctoproject.org]

On 2023-02-27 11:45, Danny Hadley via lists.yoctoproject.org wrote:

[kirkstone] `rustc` executable missing from sdk

Hello all! I am working on integrating my application CI pipeline with 
the SDK generated by our yocto CI pipeline. So far, I have been able 
to build an SDK with cargo included by adding the following 
`TOOLCHAIN_HOST_TASK` assignment to our local.conf:


```

TOOLCHAIN_HOST_TASK:append = " nativesdk-cargo"

```

and building the SDK via

```

bitbake -k -c populate_sdk 

```

However, when our application CI picks up the SDK, it looks like it is 
missing the underlying `rustc` executable; a `cargo build` command 
fails with:


```

error: could not execute process `rustc -vV` (never executed)

```

I've manually sourced the SDK environment in a shell and confirmed 
that `which` does pick up cargo but not `rustc`:


```

$ which cargo

//.sdk/sysroots/x86_64-pokysdk-linux/usr/bin/cargo
$ which rustc

$

```

Has anyone been able to populate the SDK on kirkstone with a working 
rustc/cargo toolchain?


I've also tried comparing langdale and kirkstone; it looks like on 
langdale some work was done to add `nativesdk` support to the rust 
recipe itself (via BBCLASSEXTEND in rust-target.inc). I've been trying 
to mirror those changes via `.bbappend` files but haven't quite 
figured out what strings to pull.


I'd be happy to provide any additional information that'd help triage.


Hi Danny,

Sorry for the long delay in replying. Did you ever get this to work?

Sundeep is CCed and he can help a bit if not since I'm away next week.

../Randy


Thanks!

- Danny






--
# Randy MacLeod
# Wind River Linux

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59742): https://lists.yoctoproject.org/g/yocto/message/59742
Mute This Topic: https://lists.yoctoproject.org/mt/97270242/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-