[yocto] How to remove openssl from sysroots

[Alexander Kanavin]

Ah, so are you attempting to build 32 bit apps against a 64 bit
openssl from poky? I'd say you need to either enable multilib and
build the apps against lib32-openssl:

https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#combining-multiple-versions-library-files-into-one-image

or make a super-minimal image which doesn't pull in 64 bit openssl.

Alex

2018-07-09 20:16 GMT+02:00 Alexander Kanavin <alex.kanavin at gmail.com>:
> The error message you've provided is caused by an openssl header
> referring to another header file that doesn't exist. It does not come
> from application code, but is due to openssl being incorrectly
> configured.
>
> Alex
>
> 2018-07-09 20:08 GMT+02:00 Raymond Yeung <rksyeung at hotmail.com>:
>> You may have missed one of my emails (still included here below) w.r.t.
>> where the issue came from.  It's coming from application code outside of
>> Yocto that is built as 32-bit apps, while Poky/BSP are built in 64-bit.
>>
>>
>>
>> ________________________________
>> From: Alexander Kanavin <alex.kanavin at gmail.com>
>> Sent: Monday, July 9, 2018 7:31 AM
>> To: Raymond Yeung
>> Cc: Burton, Ross; yocto at yoctoproject.org
>> Subject: Re: [yocto] How to remove openssl from sysroots
>>
>> Just fix the build issue. Look into how opensslconf.h gets created and where
>> the -32 suffix comes from and why the included file is absent.
>>
>> Seriously - that is less effort than trying to make Yocto do what it really
>> was not designed for, and certainly takes less than one week to resolve.
>>
>> Also, you do not have to use core-image-minimal or -sato, or any of the
>> standard images, if they pull in things that you do not want. Write your own
>> image recipe, and specify there precisely what you want.
>>
>> Alex
>>
>> 2018-07-09 2:32 GMT+02:00 Raymond Yeung <rksyeung at hotmail.com>:
>>
>>
>> + yocto mailing list.
>>
>> ________________________________
>> From: Raymond Yeung <rksyeung at hotmail.com>
>> Sent: Sunday, July 8, 2018 5:31 PM
>> To: Burton, Ross
>> Subject: Re: [yocto] How to remove openssl from sysroots
>>
>>
>> We're not going to integrate everything into one homogeneous package.  Poky
>> and BSP would be together.  Then, we've application codes that we'd build in
>> the same old way with SCONs the way we do before.  The two parts would link
>> together.
>>
>>
>> And we do have a number of 3rd party vendor packages beside openssl.
>> Currently, the issue with openssl is that, we run into build issue with the
>> version we got in 2016 release.  See this:
>>
>>
>>
>>
>> In file included from
>> /volume/tools/x86_64_linux.x86_64/2.1.3/sysroots/corei7-64-poky-linux/usr/include/openssl/evp.h:66:0,
>>
>>                  from src/infra/utils/obf/cv_obfuscate.c:20:
>>
>> /volume/tools/x86_64_linux.x86_64/2.1.3/sysroots/corei7-64-poky-linux/usr/include/openssl/opensslconf.h:41:36:
>> fatal error: openssl/opensslconf-32.h: No such file or directory
>>
>>
>> We plan to use 64-bit kernel, and 32-bit applications.  Perhaps that
>> explains the issue above.  We don't want to spend a lot of effort doing
>> porting simply because we adopt Yocto.  So ideally, if we could remove
>> what's in Yocto, we could integrate our apps with our own openssl; no
>> changes, including upgrade, would be needed.  We'd upgrade when we're ready.
>>
>> Another question from my team is why the "minimal" package includes
>> connectivity, which includes openssl?
>>
>> Raymond
>>
>>
>>