phosphor-bmc-state-manager: error while loading shared libraries: libfmt.so.9: cannot open shared object file: No such file or directory

[Andrew Geissler]

> On Jun 16, 2023, at 5:04 AM, Shruti Janardhan <shruti.janardhan at tcs.com> wrote:
> 
> Hi everyone,
> 
> The issue is resolved now.
> 
> 
> By checking the commit ID of the phosphor state manager recipe and OpenBmc, we realized we were using mismatched versions of commit IDs. So after fixing that, the program ran successfully.
> 

Thanks for sending a follow up on your solution Shruti. Mismatched SDK/Code has been a common issue and is why I’m working on moving the developer intro series over to just using devtool up at https://gerrit.openbmc.org/c/openbmc/docs/+/64233.

> 
> Thanks and regards,
> 
> Shruti Janardhan
> 
> 
> ________________________________
> From: openbmc <openbmc-bounces+shruti.janardhan=tcs.com at lists.ozlabs.org> on behalf of Shruti Janardhan
> Sent: Friday, June 9, 2023 5:14 PM
> To: openbmc at lists.ozlabs.org
> Cc: Sushma Patil
> Subject: phosphor-bmc-state-manager: error while loading shared libraries: libfmt.so.9: cannot open shared object file: No such file or directory
> 
> 
> Hi everyone,
> 
> While trying to run "hello world" in SDK by following the steps mentioned in the Openbmc Github page, we are getting the error: "phosphor-bmc-state-manager: error while loading shared libraries: libfmt.so.9: cannot open shared object file: No such file or directory".
> 
> 
> These are some of the steps taken by us to resolve it:
> 
>  *   Tried installing the packages libfmt-dev,libfmt-doc,libfmt-ocaml.libmft-ocaml-dev.
>  *   Using another pre-existing Qemu arm and image.
>  *   Installed and Re-built Qemu and SDK again in a new directory.
> 
> Despite trying all these steps, the error persists and we aren't sure whether the issue is with the Qemu or SDK. Could you please help us to resolve this problem.
> 
> Thanks and regards,
> Shruti Janardhan
> 
> 
> 
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain 
> confidential or privileged information. If you are 
> not the intended recipient, any dissemination, use, 
> review, distribution, printing or copying of the 
> information contained in this e-mail message 
> and/or attachments to it are strictly prohibited. If 
> you have received this communication in error, 
> please notify us by reply e-mail or telephone and 
> immediately and permanently delete the message 
> and any attachments. Thank you
> 
> 
> <winmail.dat>