Yeah building gcc alone worked.
Now I'm concerned about the health of my machine.
Thank you!

Am 27. September 2022 21:02:40 MESZ schrieb Richard Purdie <richard.purdie@...>:

On Tue, 2022-09-27 at 20:51 +0200, PHIL wrote:
Am 27. September 2022 20:40:31 MESZ schrieb Richard Purdie
<richard.purdie@...>:
On Tue, 2022-09-27 at 18:11 +0200, Edgar Mobile wrote:
Greetings,
Trying to build core-image-weston from current master fails for
gcc
12.2.0-r0 with lots of linker errors.

Names of missing functions are strange ala gen_cmulvnx16qi3.
In insn-output.o

System is an ubuntu 22.04.1 LTS Build Target is qemuarm64


We build that regularly on the autobuilder so something seems odd
here.
Could your machine have memory issues? Do you get the same issue
each
time you build?

 What do you mean with memory issues? Memory broken? Not enough
 memory? The errors are the same on every run of course I don't build
 from scratch I just retype bitbake core-image-weston. Gdb also failed
 so I took that out. 

I mean that the build system places more stress on the system than many
other workloads and we've sometimes see gcc failures like this as a
sign of failing system memory. Running memtest86 might show that up.

If recipe X is failing and you "bitbake X -c clean" and then "bitbake
X" and it doesn't fail the same way, that would be a sure sign of
memory failure or another hardware issue.

You can see here:

https://autobuilder.yoctoproject.org/typhoon/#/workers

we have Ubuntu 22.04 workers in the autobuilder and we build qemuarm64
here:

https://autobuilder.yoctoproject.org/typhoon/#/builders/42
https://autobuilder.yoctoproject.org/typhoon/#/builders/131
https://autobuilder.yoctoproject.org/typhoon/#/builders/127

so this combination is well tested which is why I suspect something
else is wrong.

Cheers,

Richard

--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.