[EXT] Re: including libubootenv in Ampere's openbmc

[Chuck Kamas]

Thank you Thang! I was able to get rid of the compilation error by
following your recommendations!

Chuck


On Tue, Jul 30, 2024 at 3:21 AM Thang Nguyen OS <
thang at amperemail.onmicrosoft.com> wrote:

>
>
> On 30 Jul 2024, at 01:32, Chuck Kamas <chuck.kamas at getcruise.com> wrote:
>
> [EXTERNAL EMAIL NOTICE: This email originated from an external sender.
> Please be mindful of safe email handling and proprietary information
> protection practices.]
>
> Hi all,
>
> I am in the process of adding swupdate to my Ampere openbmc build.
>
> I have cloned openbmc:
>
>    - git clone https://github.com/openbmc/openbmc.git
>
> configured yocto:
>
>    - . setup mtjade
>
> and compiled with no problem.
>
>    -  bitbake obmc-phosphor-image
>
> I added libubootenv to the image, in local.conf:
>
>    - IMAGE_INSTALL:append = "libubootenv"
>
> However when I build I get the following error:
>
> ERROR: Multiple .bb files are due to be built which each provide
> u-boot-fw-utils:##### | ETA: 0:00:01
>
> The Mt.Jade OpenBMC uses u-boot 2019.07 which provides u-boot-fw-utils
> from
> https://github.com/openbmc/openbmc/blob/master/meta-aspeed/recipes-bsp/u-boot/u-boot-fw-utils-aspeed-sdk_2019.04.bb
> .
> When adding libubootenv, it also provides u-boot-fw-utils
> https://github.com/openbmc/openbmc/blob/master/poky/meta/recipes-bsp/u-boot/libubootenv_0.3.5.bb
> .
> Can you manually remove one?
> As I know, libubootenv is to provide fw_setenv and fw_getenv commands but
> they are already available.
> I tried below change and I can still compile Mt.Jade successfully:
> 1. Add
> to meta-ampere/meta-jade/recipes-bsp/u-boot/u-boot-fw-utils-aspeed_%.bbappend
> DEPENDS += " libubootenv”
> 2. Remove from meta-aspeed/recipes-bsp/u-boot/
> u-boot-fw-utils-aspeed_2016.07.bb
> PROVIDES += "u-boot-fw-utils"
>
> openbmc/meta/recipes-bsp/u-boot/libubootenv_0.3.5.bb
> openbmc/meta-aspeed/recipes-bsp/u-boot/
> u-boot-fw-utils-aspeed-sdk_2019.04.bb
> A list of tasks depending on these providers is shown and may help explain
> where the dependency comes from.
> openbmc/meta/recipes-bsp/u-boot/libubootenv_0.3.5.bb has unique dependees:
> openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:
> do_populate_lic_deploy
> openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:
> do_build
> openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:
> do_create_runtime_spdx
> openbmc/meta-aspeed/recipes-bsp/u-boot/
> u-boot-fw-utils-aspeed-sdk_2019.04.bb has unique dependees:
> openbmc/meta-phosphor/recipes-phosphor/network/phosphor-network_git.bb:
> do_create_runtime_spdx
> openbmc/meta-phosphor/recipes-phosphor/trace-enable/trace-enable.bb:
> do_create_runtime_spdx
> openbmc/meta-phosphor/recipes-phosphor/network/phosphor-network_git.bb:
> do_package_qa
> openbmc/meta-phosphor/recipes-phosphor/trace-enable/trace-enable.bb:
> do_package_write_ipk
> openbmc/meta-phosphor/recipes-phosphor/clear-once/clear-once.bb:
> do_create_runtime_spdx
> openbmc/meta-phosphor/recipes-phosphor/network/phosphor-network_git.bb:
> do_package_write_ipk
> openbmc/meta-phosphor/recipes-phosphor/clear-once/clear-once.bb:
> do_package_qa
> openbmc/meta-phosphor/recipes-phosphor/clear-once/clear-once.bb:
> do_package_write_ipk
> openbmc/meta-phosphor/recipes-phosphor/trace-enable/trace-enable.bb:
> do_package_qa
> It could be that one recipe provides something the other doesn't and
> should. The following provider and runtime provider differences may be
> helpful.
> openbmc/meta/recipes-bsp/u-boot/libubootenv_0.3.5.bb has unique provides:
> libubootenv
> openbmc/meta/recipes-bsp/u-boot/libubootenv_0.3.5.bb has unique rprovides:
> libubootenv-dev
> libubootenv-bin
> libubootenv-doc
> libubootenv-dbg
> libubootenv
> libubootenv-staticdev
> ^libubootenv-locale-.*
> libubootenv-locale
> libubootenv-src
> openbmc/meta-aspeed/recipes-bsp/u-boot/
> u-boot-fw-utils-aspeed-sdk_2019.04.bb has unique provides:
> u-boot-fw-utils-aspeed-sdk
> openbmc/meta-aspeed/recipes-bsp/u-boot/
> u-boot-fw-utils-aspeed-sdk_2019.04.bb has unique rprovides:
> ^u-boot-fw-utils-aspeed-sdk-locale-.*
> u-boot-fw-utils-aspeed-sdk-src
> u-boot-fw-utils-aspeed-sdk
> u-boot-fw-utils-aspeed-sdk-doc
> u-boot-fw-utils-aspeed-sdk-locale
> u-boot-fw-utils-aspeed-sdk-dbg
> u-boot-fw-utils-aspeed-sdk-staticdev
> u-boot-fw-utils-aspeed-sdk-dev
>
>
> I have asked over on the swupdate reflector and Stefano suggested it was
> an conflict resulting from a change back in Dunfell?
>
> Any suggestions on how to resolve this error would be appreciated!
>
> Chuck
>
>
>
> *Confidentiality Note:* We care about protecting our proprietary
> information, confidential material, and trade secrets. This message may
> contain some or all of those things. Cruise will suffer material harm if
> anyone other than the intended recipient disseminates or takes any action
> based on this message. If you have received this message (including any
> attachments) in error, please delete it immediately and notify the sender
> promptly.
>
>
>

-- 


*Confidentiality Note:* We care about protecting our proprietary 
information, confidential material, and trade secrets. This message may 
contain some or all of those things. Cruise will suffer material harm if 
anyone other than the intended recipient disseminates or takes any action 
based on this message. If you have received this message (including any 
attachments) in error, please delete it immediately and notify the sender 
promptly.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20240805/150205dc/attachment.htm>