11669 2017-06-15 08:09:38 +0000 musl package doesn't provide "libc-staticdev" 2017-06-16 10:19:05 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 2.3 x86 Multiple RESOLVED NOTABUG Medium normal 2.4 1 maxin.john maxin.baby.john meta.mr.watcher meta.watcher raj.khem randy.macleod richard.purdie --- --- Don't know oldest_to_newest 74187 0 maxin.john 2017-06-15 08:09:38 +0000 When we try to build libc-staticdev (glibc): # bitbake libc-staticdev ERROR: Nothing PROVIDES 'libc-staticdev'. Close matches: glibc RPROVIDES libc-staticdev For musl: # bitbake libc-staticdev ERROR: Nothing PROVIDES 'libc-staticdev' musl libc also should provide staticdev package. This will help "musl" based SDKs to build applications using static libraries. 74188 1 maxin.john 2017-06-15 08:10:54 +0000 Adding Khem in CC List 74212 2 richard.purdie 2017-06-15 14:58:48 +0000 bitbake <package> is not a supported syntax, it needs to be a recipe target. Also, we disable static libraries by default now. We can't stop glibc building some of them so we package those but musl is probably honouring the global settings more. We may therefore need more info here. 74215 3 richard.purdie 2017-06-15 15:01:48 +0000 See question above 74235 4 raj.khem 2017-06-15 15:55:16 +0000 (In reply to comment #2) > bitbake <package> is not a supported syntax, it needs to be a recipe target. > > Also, we disable static libraries by default now. We can't stop glibc > building some of them so we package those but musl is probably honouring the > global settings more. We may therefore need more info here. musl does build .a files and puts them into musl-staticdev we probably just need a PROVIDES directive but you could also use ${TCLIBC}-staticdev to be libc agnostic then we dont need PROVIDES 74273 5 maxin.john 2017-06-16 10:19:05 +0000 Hi RP, Khem, Thanks for commenting on this. This bug was created as part of a suggestion from this thread: https://lists.yoctoproject.org/pipermail/yocto/2017-June/036632.html " That should perhaps be "libc-staticdev" so the same instructions work for musl (although it looks like currently musl doesn't rprovide libc-staticdev so that would need to be fixed too). " As RP mentioned, we are disabling static libraries by default these days. So, we don't have to add PROVIDES in musl recipe. Instead, as Khem mentioned, add this line in local.conf : "TOOLCHAIN_TARGET_TASK += "${TCLIBC}-staticdev" and we will get required ".a" files for the libc (glibc or musl) in SDK. (In reply to comment #4) > (In reply to comment #2) > > bitbake <package> is not a supported syntax, it needs to be a recipe target. > > > > Also, we disable static libraries by default now. We can't stop glibc > > building some of them so we package those but musl is probably honouring the > > global settings more. We may therefore need more info here. > > musl does build .a files and puts them into musl-staticdev we probably just > need a PROVIDES directive but you could also use > > ${TCLIBC}-staticdev to be libc agnostic then we dont need PROVIDES