From: Patrick Williams <patrick@stwcx.xyz>
To: "Wang, Kuiying" <kuiying.wang@intel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
Brad Bishop <bradleyb@fuzziesquirrel.com>
Subject: Re: Need update CI build config for new repo smbios-mdr.
Date: Wed, 2 Sep 2020 10:49:44 -0500 [thread overview]
Message-ID: <20200902154944.GW3532@heinlein> (raw)
In-Reply-To: <SN6PR11MB352047845E48681E8F71B139902F0@SN6PR11MB3520.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]
On Wed, Sep 02, 2020 at 02:02:00AM +0000, Wang, Kuiying wrote:
> Hi Williams,
> The key thing is sdbusplus interface is not match.
> You could config CI based on this patch https://gerrit.openbmc-project.xyz/#/c/openbmc/smbios-mdr/+/36011/
> That's ok, if it can pass the build.
>
> Thanks,
> Kwin.
>
Here is a snippet of the compile log:
/home/jenkins-slave/workspace/ci-repository/openbmc/smbios-mdr/src/cpuinfo_main.cpp:34:10: fatal error: peci.h: No such file or directory
34 | #include <peci.h>
| ^~~~~~~~
compilation terminated.
This one might be a missing dependency? Where is 'peci.h' from? Is it
from a kernel header for the ioctls or some other repository? Do you
need to stub this out when building on x86?
make[2]: *** [CMakeFiles/cpuinfoapp.dir/build.make:63: CMakeFiles/cpuinfoapp.dir/src/cpuinfo_main.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:78: CMakeFiles/cpuinfoapp.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
In file included from /home/jenkins-slave/workspace/ci-repository/openbmc/smbios-mdr/src/cpu.cpp:17:
/home/jenkins-slave/workspace/ci-repository/openbmc/smbios-mdr/include/cpu.hpp:113:17: error: âstd::string phosphor::smbios::Cpu::processorSocket(std::string)â marked âoverrideâ, but does not override
113 | std::string processorSocket(std::string value) override;
This appears to be a case where the current phosphor-dbus-interfaces
doesn't match whatever your commit is trying to do. You've got
additional methods for handling dbus properties, but those properties do
not exist in phosphor-dbus-interface's Cpu interface.
I suspect you're trying to implement
xyz/openbmc_project/Inventory/Item/Cpu, which has a 'Socket' property
but not a 'ProcessorSocket'. If I recall, this happened in the code
review where the "Processor" part was requested to be removed since it
was redundant.
There are a number of other properties in your compile fail that need
similar updating.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-02 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SN6PR11MB35203BE16B23BAD1193FCB9F90550@SN6PR11MB3520.namprd11.prod.outlook.com>
[not found] ` <5a9a43046be525f9ed5d23bc40eac14d4ed8d53c.camel@fuzziesquirrel.com>
2020-08-31 1:45 ` Need update CI build config for new repo smbios-mdr Wang, Kuiying
2020-09-01 16:23 ` Patrick Williams
2020-09-01 16:41 ` Patrick Williams
2020-09-02 2:02 ` Wang, Kuiying
2020-09-02 5:46 ` 郁雷
2020-09-02 5:53 ` Wang, Kuiying
2020-09-02 15:49 ` Patrick Williams [this message]
2020-09-02 18:24 ` Bills, Jason M
2020-09-02 21:46 ` Ren, Zhikui
2020-09-03 4:17 ` Wang, Kuiying
2020-09-02 2:22 ` Wang, Kuiying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200902154944.GW3532@heinlein \
--to=patrick@stwcx.xyz \
--cc=bradleyb@fuzziesquirrel.com \
--cc=kuiying.wang@intel.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.