openBMC on raspberry Pi 4

[VinayWolf]

Hello all,
I was trying to build openBMC for raspberry pi. I was following the https://gerrit.openbmc.org/c/openbmc/meta-evb/+/17058/1/meta-evb-raspberrypi/README.md#29. When i do bitbake that time i m getting an error.

WARNING: /home/vinay/openBMC/openbmc/meta/lib/oe/maketype.py:99: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it will stop working
if not isinstance(obj, collections.Callable):

Loading cache: 100% |#########################################################################################################################################| Time: 0:00:00
Loaded 3073 entries from dependency cache.
WARNING: /home/vinay/openBMC/openbmc/meta-evb/meta-evb-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.18.bb: Exception during build_dependencies for PKG_kernel-base:--
WARNING: /home/vinay/openBMC/openbmc/meta-evb/meta-evb-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.18.bb: Error during finalise of /home/vinay/openBMC/openbmc/meta-evb/meta-evb-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.18.bb
ERROR: ExpansionError during parsing /home/vinay/openBMC/openbmc/meta-evb/meta-evb-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.18.bb | ETA: 0:00:00
Traceback (most recent call last):
bb.data_smart.ExpansionError: Failure expanding variable PKG_kernel-base, expression was kernel-${@legitimize_package_name('${@get_kernelversion_headers('/home/vinay/openBMC/openbmc/build/tmp/work/raspberrypi_cm3-openbmc-linux-gnueabi/linux-raspberrypi/1_4.18+git${SRCPV}-r0/linux-raspberrypi_cm3-standard-build')}')} which triggered exception SyntaxError: invalid syntax (PKG_kernel-base, line 1)

Summary: There were 3 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

So what can be the possible issue/solution??
i can see that this guy tried n it worked.
#3581 (comment)

[mdmillerii]

This looks to be an issue with meta -raspberrypi and not the integration with phosphor and the rest of the OpenBMC project.

You can test this hypothesis by building an image according to documentation for an upstream build. After confirming bring it to with them.

The OpenBMC project synchronizes with upstream periodically and will pick up changes made there, although you may point out recent changes that are needed. We occasionally backport individual changesets as patches,(but generally prefers to just sync again mus release.