On Mon, 2018-12-03 at 09:52 +0100, Richard Weinberger wrote: > On Wed, Nov 28, 2018 at 9:26 PM Richard Weinberger > <[email protected]> wrote: > > Richard, > > > > On Wed, Nov 28, 2018 at 9:42 AM Richard Purdie > > <[email protected]> wrote: > > > > But it seems that building and SDK is currently > > > > broken/disabled: > > > > > > > http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=e153efde9754a650e555f46cba09680baabd7d7e > > > > > > I see a bug was opened for this but its not valid and this > > > shouldn't be > > > an issue. Keep in mind that an SDK contains all multilibs so > > > "bitbake > > > X-image -c populate_sdk" would be equivalent to "bitbake libXX-X- > > > image > > > -c populate_sdk" and be the same thing. One didn't work so we > > > remove > > > that. > > > > My idea was having a 32bit only SDK. In my case I really don't need > > 64bit userspace. > > On the other hand, having both 32bit and 64bit libs in the SDK is > > not > > a big deal right now. > > > > So I did "bitbake my-image -c populate_sdk" but the resulting SDK > > seems to contain no > > 32bits libraries. > > TOOLCHAIN_TARGET_TASK contains "openssl", so I expected libssl.so > > present. > > I did a search for libssl.so and found these files in the SDK > > install directory: > > > > ./tmp/sysroots/mymachine/usr/lib64/libssl.so.1.0.2 > > ./tmp/sysroots/mymachine/usr/lib/libssl.so.1.0.2 > > > > Both files are 64bit shared libraries :-( > > > > What do I miss? > > *kind ping*
This is the bug that Qi opened. The code doesn't do what you want right now and I'm not sure how easy/hard it would be to make it do the above :( Sorry, I hadn't realised we had this problem until you dived into it although it is kind of obvious in hindsight... Cheers, Richard -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
