Re: [yocto] How to remove openssl from sysroots
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 Sent: Monday, July 9, 2018 7:31 AM To: Raymond Yeung Cc: Burton, Ross; yocto@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 mailto:rksye...@hotmail.com>>: + yocto mailing list. From: Raymond Yeung mailto:rksye...@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 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to remove openssl from sysroots
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 : > 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 : >> 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 >> Sent: Monday, July 9, 2018 7:31 AM >> To: Raymond Yeung >> Cc: Burton, Ross; yocto@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 : >> >> >> + yocto mailing list. >> >> >> From: Raymond Yeung >> 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 >> >> >> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to remove openssl from sysroots
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 : > 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 > Sent: Monday, July 9, 2018 7:31 AM > To: Raymond Yeung > Cc: Burton, Ross; yocto@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 : > > > + yocto mailing list. > > ________ > From: Raymond Yeung > 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 > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
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 : > > + yocto mailing list. > > -- > *From:* Raymond Yeung > *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 > > ---------- > *From:* Burton, Ross > *Sent:* Sunday, July 8, 2018 1:06 AM > > *To:* Raymond Yeung > *Cc:* yocto@yoctoproject.org > *Subject:* Re: [yocto] How to remove openssl from sysroots > > I strongly recommend you just write a recipe that builds openssl as you > wish, instead of building it out of the build system and somehow getting it > into the images. The problem is that how do you intend to build software > against openssl if it can't link to the one in oe-core (as you don't want > it) or your custom one (because it doesn't exist yet). > > The workaround - which is horrible - would be to use a rootfs postprocess > hook to forcibly remove the openssl packages from the rootfs, and then drop > in your own files. > > Ross > > On 8 July 2018 at 07:14, Raymond Yeung wrote: > > We have a shell script that builds openssl. It uses the native makefiles > from the open source project. There's no recipe. I suppose we define a > recipe for this out-of-tree sources. > > > Still, if we could yank out embedded openssl easily, that would be the > best. > > > Raymond > > > -- > *From:* Burton, Ross > *Sent:* Saturday, July 7, 2018 3:41 PM > *To:* Raymond Yeung > *Cc:* yocto@yoctoproject.org > *Subject:* Re: [yocto] How to remove openssl from sysroots > > Presumably you've a recipe for the vendor openssl. If it has the same > name but is a different version then just set PREFERRED_VERSION. If > it has a different name too, it should PROVIDE openssl and you can > just set PREFERRED_PROVIDER. > > If it doesn't do either of those things, then it is broken. > > Ross > > On 6 July 2018 at 23:06, Raymond Yeung wrote: > > I've changed the subject heading to make it more specific to our problem. > > Hopefully this generates some responses. > > > > > > It has been blocking us for close to one week now. We want to use our > 3rd > > party vendor openssl, not the one that comes with the source. > Apparently, > > even with "minimal" instead of "base" or "sato" cannot exclude it. > > > > > > Any idea [e.g. how do we systematically find out how it's included now, > and > > possibly what other packages/recipes we may also need to remove due to > > dependency]? > > > > > > Thanks, > > > > Raymond > > > > > > > > > > From: Raymond Yeung > > Sent:
Re: [yocto] How to remove openssl from sysroots
+ yocto mailing list. From: Raymond Yeung 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 From: Burton, Ross Sent: Sunday, July 8, 2018 1:06 AM To: Raymond Yeung Cc: yocto@yoctoproject.org Subject: Re: [yocto] How to remove openssl from sysroots I strongly recommend you just write a recipe that builds openssl as you wish, instead of building it out of the build system and somehow getting it into the images. The problem is that how do you intend to build software against openssl if it can't link to the one in oe-core (as you don't want it) or your custom one (because it doesn't exist yet). The workaround - which is horrible - would be to use a rootfs postprocess hook to forcibly remove the openssl packages from the rootfs, and then drop in your own files. Ross On 8 July 2018 at 07:14, Raymond Yeung mailto:rksye...@hotmail.com>> wrote: We have a shell script that builds openssl. It uses the native makefiles from the open source project. There's no recipe. I suppose we define a recipe for this out-of-tree sources. Still, if we could yank out embedded openssl easily, that would be the best. Raymond From: Burton, Ross mailto:ross.bur...@intel.com>> Sent: Saturday, July 7, 2018 3:41 PM To: Raymond Yeung Cc: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org> Subject: Re: [yocto] How to remove openssl from sysroots Presumably you've a recipe for the vendor openssl. If it has the same name but is a different version then just set PREFERRED_VERSION. If it has a different name too, it should PROVIDE openssl and you can just set PREFERRED_PROVIDER. If it doesn't do either of those things, then it is broken. Ross On 6 July 2018 at 23:06, Raymond Yeung mailto:rksye...@hotmail.com>> wrote: > I've changed the subject heading to make it more specific to our problem. > Hopefully this generates some responses. > > > It has been blocking us for close to one week now. We want to use our 3rd > party vendor openssl, not the one that comes with the source. Apparently, > even with "minimal" instead of "base" or "sato" cannot exclude it. > > > Any idea [e.g. how do we systematically find out how it's included now, and > possibly what other packages/recipes we may also need to remove due to > dependency]? > > > Thanks, > > Raymond > > > > > From: Raymond Yeung mailto:rksye...@hotmail.com>> > Sent: Monday, July 2, 2018 11:05 PM > To: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org> > Subject: How to remove a package from a build > > > We've our own non-yocto openssl that we want to use. At the moment, we're > using "sato" image, rather than "minimal" and includes its openssl that is > out-of-date. What is the best way to exclude it from our image (and from > sysroots)? > > > We have thought about two ideas - > > > Use smaller image like core-image-base, or core-image-full-cmdline (but not > -minimal that may remove too much functionality). > Use INSTALL_IMAGE_remove += " openssl" > > > Would either one work? Also, how do I follow the .bb files etc (e.g. > starting from the one for sato) to trace down which sub-package includes > openssl? > > > Thanks, > > Raymond > > > -- >
Re: [yocto] How to remove openssl from sysroots
On Sun, Jul 8, 2018 at 7:04 PM, Philip Balister wrote: > On 07/06/2018 03:06 PM, Raymond Yeung wrote: >> I've changed the subject heading to make it more specific to our problem. >> Hopefully this generates some responses. >> >> It has been blocking us for close to one week now. We want to use our 3rd >> party vendor openssl, not the one that comes with the source. Apparently, >> even with "minimal" instead of "base" or "sato" cannot exclude it. >> >> Any idea [e.g. how do we systematically find out how it's included now, and >> possibly what other packages/recipes we may also need to remove due to >> dependency]? > > I tend to use the ouput of the buildhistory class when I have these > questions. An alternative quick and dirty approach is to make the recipe unbuildable. If the recipe is unbuildable but needed by something then the bitbake error message will give the dependency chain. You can make a recipe unbuildable for the target by adding the following to the recipe: COMPATIBLE_HOST_class-target = 'null' Note that there are two openssl recipes in recent oe-core (v1.0.x and v1.1.x). For this experiment you will need to make BOTH of them unbuildable. This seems like a somewhat pointless path to be going down though. If you remove all packages which depend on openssl from the target rootfs then you won't need to add in your 3rd party vendor openssl any more... since nothing is going to use it. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to remove openssl from sysroots
On 07/06/2018 03:06 PM, Raymond Yeung wrote: > I've changed the subject heading to make it more specific to our problem. > Hopefully this generates some responses. > > > It has been blocking us for close to one week now. We want to use our 3rd > party vendor openssl, not the one that comes with the source. Apparently, > even with "minimal" instead of "base" or "sato" cannot exclude it. > > > Any idea [e.g. how do we systematically find out how it's included now, and > possibly what other packages/recipes we may also need to remove due to > dependency]? I tend to use the ouput of the buildhistory class when I have these questions. Philip > > > Thanks, > > Raymond > > > > From: Raymond Yeung > Sent: Monday, July 2, 2018 11:05 PM > To: yocto@yoctoproject.org > Subject: How to remove a package from a build > > > We've our own non-yocto openssl that we want to use. At the moment, we're > using "sato" image, rather than "minimal" and includes its openssl that is > out-of-date. What is the best way to exclude it from our image (and from > sysroots)? > > > We have thought about two ideas - > > > 1. Use smaller image like core-image-base, or core-image-full-cmdline (but > not -minimal that may remove too much functionality). > 2. Use INSTALL_IMAGE_remove += " openssl" > > > Would either one work? Also, how do I follow the .bb files etc (e.g. > starting from the one for sato) to trace down which sub-package includes > openssl? > > > Thanks, > > Raymond > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to remove openssl from sysroots
We have a shell script that builds openssl. It uses the native makefiles from the open source project. There's no recipe. I suppose we define a recipe for this out-of-tree sources. Still, if we could yank out embedded openssl easily, that would be the best. Raymond From: Burton, Ross Sent: Saturday, July 7, 2018 3:41 PM To: Raymond Yeung Cc: yocto@yoctoproject.org Subject: Re: [yocto] How to remove openssl from sysroots Presumably you've a recipe for the vendor openssl. If it has the same name but is a different version then just set PREFERRED_VERSION. If it has a different name too, it should PROVIDE openssl and you can just set PREFERRED_PROVIDER. If it doesn't do either of those things, then it is broken. Ross On 6 July 2018 at 23:06, Raymond Yeung wrote: > I've changed the subject heading to make it more specific to our problem. > Hopefully this generates some responses. > > > It has been blocking us for close to one week now. We want to use our 3rd > party vendor openssl, not the one that comes with the source. Apparently, > even with "minimal" instead of "base" or "sato" cannot exclude it. > > > Any idea [e.g. how do we systematically find out how it's included now, and > possibly what other packages/recipes we may also need to remove due to > dependency]? > > > Thanks, > > Raymond > > > > > From: Raymond Yeung > Sent: Monday, July 2, 2018 11:05 PM > To: yocto@yoctoproject.org > Subject: How to remove a package from a build > > > We've our own non-yocto openssl that we want to use. At the moment, we're > using "sato" image, rather than "minimal" and includes its openssl that is > out-of-date. What is the best way to exclude it from our image (and from > sysroots)? > > > We have thought about two ideas - > > > Use smaller image like core-image-base, or core-image-full-cmdline (but not > -minimal that may remove too much functionality). > Use INSTALL_IMAGE_remove += " openssl" > > > Would either one work? Also, how do I follow the .bb files etc (e.g. > starting from the one for sato) to trace down which sub-package includes > openssl? > > > Thanks, > > Raymond > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto yocto Info Page<https://lists.yoctoproject.org/listinfo/yocto> lists.yoctoproject.org Discussion of all things about the Yocto Project. Read our Community Guidelines or learn more about how to participate in other community discussions. Subscribe before posting to bypass moderation. > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to remove openssl from sysroots
If the issue is that openssl is 'out of date', then oe-core already provides a 1.1 version that can be selected via PREFERRED_VERSION as well. What is the specific need for the 3rd party version? Alex 2018-07-08 0:41 GMT+02:00 Burton, Ross : > Presumably you've a recipe for the vendor openssl. If it has the same > name but is a different version then just set PREFERRED_VERSION. If > it has a different name too, it should PROVIDE openssl and you can > just set PREFERRED_PROVIDER. > > If it doesn't do either of those things, then it is broken. > > Ross > > On 6 July 2018 at 23:06, Raymond Yeung wrote: >> I've changed the subject heading to make it more specific to our problem. >> Hopefully this generates some responses. >> >> >> It has been blocking us for close to one week now. We want to use our 3rd >> party vendor openssl, not the one that comes with the source. Apparently, >> even with "minimal" instead of "base" or "sato" cannot exclude it. >> >> >> Any idea [e.g. how do we systematically find out how it's included now, and >> possibly what other packages/recipes we may also need to remove due to >> dependency]? >> >> >> Thanks, >> >> Raymond >> >> >> >> >> From: Raymond Yeung >> Sent: Monday, July 2, 2018 11:05 PM >> To: yocto@yoctoproject.org >> Subject: How to remove a package from a build >> >> >> We've our own non-yocto openssl that we want to use. At the moment, we're >> using "sato" image, rather than "minimal" and includes its openssl that is >> out-of-date. What is the best way to exclude it from our image (and from >> sysroots)? >> >> >> We have thought about two ideas - >> >> >> Use smaller image like core-image-base, or core-image-full-cmdline (but not >> -minimal that may remove too much functionality). >> Use INSTALL_IMAGE_remove += " openssl" >> >> >> Would either one work? Also, how do I follow the .bb files etc (e.g. >> starting from the one for sato) to trace down which sub-package includes >> openssl? >> >> >> Thanks, >> >> Raymond >> >> >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to remove openssl from sysroots
I strongly recommend you just write a recipe that builds openssl as you wish, instead of building it out of the build system and somehow getting it into the images. The problem is that how do you intend to build software against openssl if it can't link to the one in oe-core (as you don't want it) or your custom one (because it doesn't exist yet). The workaround - which is horrible - would be to use a rootfs postprocess hook to forcibly remove the openssl packages from the rootfs, and then drop in your own files. Ross On 8 July 2018 at 07:14, Raymond Yeung wrote: > We have a shell script that builds openssl. It uses the native makefiles > from the open source project. There's no recipe. I suppose we define a > recipe for this out-of-tree sources. > > > Still, if we could yank out embedded openssl easily, that would be the > best. > > > Raymond > > > -- > *From:* Burton, Ross > *Sent:* Saturday, July 7, 2018 3:41 PM > *To:* Raymond Yeung > *Cc:* yocto@yoctoproject.org > *Subject:* Re: [yocto] How to remove openssl from sysroots > > Presumably you've a recipe for the vendor openssl. If it has the same > name but is a different version then just set PREFERRED_VERSION. If > it has a different name too, it should PROVIDE openssl and you can > just set PREFERRED_PROVIDER. > > If it doesn't do either of those things, then it is broken. > > Ross > > On 6 July 2018 at 23:06, Raymond Yeung wrote: > > I've changed the subject heading to make it more specific to our problem. > > Hopefully this generates some responses. > > > > > > It has been blocking us for close to one week now. We want to use our > 3rd > > party vendor openssl, not the one that comes with the source. > Apparently, > > even with "minimal" instead of "base" or "sato" cannot exclude it. > > > > > > Any idea [e.g. how do we systematically find out how it's included now, > and > > possibly what other packages/recipes we may also need to remove due to > > dependency]? > > > > > > Thanks, > > > > Raymond > > > > > > > > > > From: Raymond Yeung > > Sent: Monday, July 2, 2018 11:05 PM > > To: yocto@yoctoproject.org > > Subject: How to remove a package from a build > > > > > > We've our own non-yocto openssl that we want to use. At the moment, > we're > > using "sato" image, rather than "minimal" and includes its openssl that > is > > out-of-date. What is the best way to exclude it from our image (and from > > sysroots)? > > > > > > We have thought about two ideas - > > > > > > Use smaller image like core-image-base, or core-image-full-cmdline (but > not > > -minimal that may remove too much functionality). > > Use INSTALL_IMAGE_remove += " openssl" > > > > > > Would either one work? Also, how do I follow the .bb files etc (e.g. > > starting from the one for sato) to trace down which sub-package includes > > openssl? > > > > > > Thanks, > > > > Raymond > > > > > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > yocto Info Page <https://lists.yoctoproject.org/listinfo/yocto> > lists.yoctoproject.org > Discussion of all things about the Yocto Project. Read our Community > Guidelines or learn more about how to participate in other community > discussions. Subscribe before posting to bypass moderation. > > > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to remove openssl from sysroots
Presumably you've a recipe for the vendor openssl. If it has the same name but is a different version then just set PREFERRED_VERSION. If it has a different name too, it should PROVIDE openssl and you can just set PREFERRED_PROVIDER. If it doesn't do either of those things, then it is broken. Ross On 6 July 2018 at 23:06, Raymond Yeung wrote: > I've changed the subject heading to make it more specific to our problem. > Hopefully this generates some responses. > > > It has been blocking us for close to one week now. We want to use our 3rd > party vendor openssl, not the one that comes with the source. Apparently, > even with "minimal" instead of "base" or "sato" cannot exclude it. > > > Any idea [e.g. how do we systematically find out how it's included now, and > possibly what other packages/recipes we may also need to remove due to > dependency]? > > > Thanks, > > Raymond > > > > > From: Raymond Yeung > Sent: Monday, July 2, 2018 11:05 PM > To: yocto@yoctoproject.org > Subject: How to remove a package from a build > > > We've our own non-yocto openssl that we want to use. At the moment, we're > using "sato" image, rather than "minimal" and includes its openssl that is > out-of-date. What is the best way to exclude it from our image (and from > sysroots)? > > > We have thought about two ideas - > > > Use smaller image like core-image-base, or core-image-full-cmdline (but not > -minimal that may remove too much functionality). > Use INSTALL_IMAGE_remove += " openssl" > > > Would either one work? Also, how do I follow the .bb files etc (e.g. > starting from the one for sato) to trace down which sub-package includes > openssl? > > > Thanks, > > Raymond > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to remove openssl from sysroots
I've changed the subject heading to make it more specific to our problem. Hopefully this generates some responses. It has been blocking us for close to one week now. We want to use our 3rd party vendor openssl, not the one that comes with the source. Apparently, even with "minimal" instead of "base" or "sato" cannot exclude it. Any idea [e.g. how do we systematically find out how it's included now, and possibly what other packages/recipes we may also need to remove due to dependency]? Thanks, Raymond From: Raymond Yeung Sent: Monday, July 2, 2018 11:05 PM To: yocto@yoctoproject.org Subject: How to remove a package from a build We've our own non-yocto openssl that we want to use. At the moment, we're using "sato" image, rather than "minimal" and includes its openssl that is out-of-date. What is the best way to exclude it from our image (and from sysroots)? We have thought about two ideas - 1. Use smaller image like core-image-base, or core-image-full-cmdline (but not -minimal that may remove too much functionality). 2. Use INSTALL_IMAGE_remove += " openssl" Would either one work? Also, how do I follow the .bb files etc (e.g. starting from the one for sato) to trace down which sub-package includes openssl? Thanks, Raymond -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
