10954 2017-01-23 15:55:27 +0000 dynamically detect dependency on libgcc 2026-02-26 16:01:14 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain unspecified x86 Multiple NEW Medium enhancement 6.1 1 patrick.ohly ross.burton david.reyna javier.tia meta.mr.watcher meta.watcher randy.macleod richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 70021 0 patrick.ohly 2017-01-23 15:55:27 +0000 Some pthread functions in glibc, for example pthread_cancel, depend on glibc and open it dynamically at runtime. If not installed, applications calling those pthread functions fail with: libgcc_s.so.1 must be installed for pthread_cancel to work Adding RDEPENDS += "libgcc" to application recipes is the wrong solution, because they shouldn't have to know about this glibc-internal implementation detail, nor should they have to check whether they are linked against glibc in the first place. Adding RDEPENDS += "libgcc" to glibc itself would be better, but some people are concerned about the wasted disk space when it is not actually needed by anything in the image. The right solution therefore seems to be an enhancement of the automatic shlib analysis code. It needs to know which pthread functions need libgcc and if glibc is used and these functions are called, add the RDEPENDS for the calling application automatically. 95428 1 randy.macleod 2023-04-21 18:45:44 +0000 Moved en masse from 4.2 to 4.3 by Randy. 99833 2 ross.burton 2024-10-10 16:35:32 +0000 libgcc_s.so is 130K. I think we should just add RDEPENDS:${PN} += "libgcc" to glibc. 100206 3 richard.purdie 2024-11-19 13:28:21 +0000 We've come this far without doing that and we do have embedded users so I'd prefer to avoid doing that if we can...