15594 2024-09-12 08:52:50 +0000 AB-INT: ld segfault during webruntime-clang build 2024-11-05 11:30:44 +0000 1 1 10 QA/Testing Functional (self) Testing general unspecified x86 Multiple RESOLVED FIXED AB-INT Medium normal 5.2 1 mathieu.dubois-briand ross.burton Martin.Jansa nvhieudt11 ross.burton --- --- No (bug/feature does not impact docs) oldest_to_newest 99651 0 mathieu.dubois-briand 2024-09-12 08:52:50 +0000 Happened during meta-webosose test on alma9-ty-2 https://autobuilder.yoctoproject.org/typhoon/#/builders/163/builds/40/steps/13/logs/stdio | collect2: fatal error: ld terminated with signal 11 [Segmentation fault], core dumped | compilation terminated. ... | WARNING: Backtrace (BB generated script): | #1: do_compile, /home/pokybuild/yocto-worker/meta-webosose/build/build/tmp-glibc/work/qemux86_64-webos-linux/webruntime-clang/108.0.5359.217-32-r4/temp/run.do_compile.795229, line 167 | #2: main, /home/pokybuild/yocto-worker/meta-webosose/build/build/tmp-glibc/work/qemux86_64-webos-linux/webruntime-clang/108.0.5359.217-32-r4/temp/run.do_compile.795229, line 351 99656 1 ross.burton 2024-09-12 14:42:16 +0000 I wonder if this is actually an OOM in disguise? Martin, have you seen webruntime-clang fail to build like this before? 99670 2 nvhieudt11 2024-09-17 07:37:07 +0000 Hi, I've reproduced the problem on my docker container (almalinux9). Here are dmesg log, segmentation fault when call ld.gold command: > [23896458.778136] ld.gold[2567414]: segfault at 18 ip 00007f8059e72cfe sp 00007ffded12c060 error 4 in libc.so.6[7f8059e01000+175000] > [23896690.710362] ld.gold[2576511]: segfault at 1fffffff9 ip 00007fd4ae0b3cfe sp 00007fff3ead3d20 error 4 in libc.so.6[7fd4ae042000+175000] I tested with the worked around from Martin and webruntime can be built with this commit: https://github.com/webOS-ports/meta-webos-ports/commit/fffd8293be843b839c6bfe809a55277ed1502e2e (drop use_gold) Actually we have already upgraded webruntime-clang version from 108 to 120 and it builds well on almalinux9, but just LG internals. We are waiting for next webosose release (maybe next month) 99760 3 ross.burton 2024-10-03 15:00:11 +0000 Thanks Hieu. Is that commit merged, and what's the timeline for the new webose release? 99841 4 mathieu.dubois-briand 2024-10-11 07:23:01 +0000 meta-webosose rocky9-ty-1 https://autobuilder.yoctoproject.org/typhoon/#/builders/163/builds/46/steps/13/logs/stdio 99849 5 nvhieudt11 2024-10-12 08:46:35 +0000 Hi Ross and Mathieu, I saw the same issue on rocky9-ty-1 yesterday. I asked the person in charge of OSE about the release plan, but they have too many issues and cannot release it right away, and they need to discuss/estimate and come up with a release plan. Sorry for the inconvenience. I also hope they have an answer soon. 100035 6 mathieu.dubois-briand 2024-10-25 10:09:06 +0000 meta-webosose rocky9-vk-2 https://valkyrie.yoctoproject.org/#/builders/51/builds/8/steps/13/logs/stdio 100103 7 nvhieudt11 2024-11-05 09:26:26 +0000 Hi Ross and Mathieu, I would like to inform you that meta-webosose has been released on Github: https://github.com/webosose/meta-webosose/commits/kirkstone-webos. Hopefully we won't have this problem again. We have upgraded meta-qt6 from "6.6.0" to version "6.7.2". So could you please help to update the config.py and schedulers.py? > https://git.yoctoproject.org/yocto-autobuilder2/tree/config.py#n63 > https://git.yoctoproject.org/yocto-autobuilder2/tree/schedulers.py#n166 Thank you very much! 100111 8 ross.burton 2024-11-05 11:30:44 +0000 Thanks Hieu for the update, and thanks Mattieu for the patch. The AB is being updated now so I'll close this and we'll reopen if it happens again.