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 <http://www.general-logic.com/>
www.linkedin.com/in/daniele-lugli <http://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]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to