15083 2023-03-28 14:10:30 +0000 libgcc_s.so wrong file format 2023-03-30 15:10:20 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 3.1.24 All Multiple RESOLVED NOTABUG Medium+ normal 3.1.25 1 virendrak virendrak meta.mr.watcher meta.watcher randy.macleod ross.burton steve sundeep.kokkonda --- --- No (bug/feature does not impact docs) oldest_to_newest 95202 0 virendrak 2023-03-28 14:10:30 +0000 It was detected a change on mainline builds when the switch to gcc 9.5 was made from 9.3 after recent upgrade in poky dunfell upgrade gcc to 9.5. Previously libgcc_s.so was a symbolic link to libgcc_s.so.1, after the update to gcc 9.5 it stopped being a link and it is just a library file with no format. libgcc1 -> Has the libgcc_s.so.1 file on both. libgcc1-dev -> Has the symbolic link in gcc 9.3, but on gcc 9.5 it has a broken library. 95228 1 randy.macleod 2023-03-30 14:41:47 +0000 Virendra, Thanks for reporting the bug. Please confirm that his is the dunfell branch. Can you explain when the update from 9.2 to 9.5 gcc was? Can more provide more information about how to reproduce the bug? Steve Sakoman may also take a look at this. 95234 2 ross.burton 2023-03-30 14:57:29 +0000 99% sure that this is the .so file changing from a symlink to a linker script, which is absolutely fine. 95235 3 ross.burton 2023-03-30 15:10:20 +0000 $ cat /yocto/ross/build-dunfell/tmp/work/core2-64-poky-linux/libgcc/9.5.0-r0/packages-split/libgcc-dev/lib/libgcc_s.so /* GNU ld script Use the shared library, but some functions are only in the static library. */ GROUP ( libgcc_s.so.1 -lgcc ) That's not broken, that's a linker script. This is perfectly valid.