Hi Kishen, Thank you for your response.
With your patch now I am able to build the Iotivity-0.92. But when I run the sampleconsumer apllication I am getting the following error. -> listen Callback(): failed to create resource. clientResponse: But sampleprovider is working fine. For earlier versions it is working. Please help me for resolving this issue. Regards, Raghavendra K. ________________________________________ From: Maloor, Kishen <[email protected]> Sent: Tuesday, September 22, 2015 3:09 AM To: Raghavendra Kakarla; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Getting error while building the Iotivity-0.9.2 in yocto Hi, You compilation error isn?t because of Yocto or the recipe. It is failing because a test framework being used for the IoTivity service layer?s unit tests, called Hippomocks, has some architecture-specific code which has been specified for x86 and ARM, but not for MIPS. Resolving this requires a separate discussion and and input from the developers of the service layer?s unit tests. But for now, I have what might be an interim hack for you to get your build to complete so you can develop against IoTivity. Attached is a patch. Run your build as usual and once it fails, go into ${S} (this is the same as ${WORKDIR}/iotivity-0.9.2/) and then execute: patch -p1 < hippomocks_mips_patch Ensure that the patch command didn?t show any errors. Now re-run your build (using bitbake) and it should proceed to completion. Let me know if that didn?t work. -Kishen. On 9/20/15, 10:55 PM, "Raghavendra Kakarla" <Raghavendra.Kakarla at inedasystems.com> wrote: >Hi Kishen, > >We are executing the yocto build on ubuntu-14.04 version. > >We are building the Iovotivity for the MIPS32 architecture. > >I am attaching the log.do_fetch,log.do_compile and run.do_compile files >to this mail. > >Please help me in resolving this issue. > >Regards, >Raghavendra K. > > >________________________________________ >From: Maloor, Kishen <kishen.maloor at intel.com> >Sent: Tuesday, September 8, 2015 7:04 AM >To: Raghavendra Kakarla; iotivity-dev at lists.iotivity.org >Subject: Re: [dev] Getting error while building the Iotivity-0.9.2 in >yocto > >Hi, > > >On what OS are you executing the Yocto build? What BSP are you building >IoTivity with? What is the architecture of your target? >Could you send the contents of log.do_fetch, log.do_compile and >run.do_compile from your build? > >As I previously mentioned, the errors you indicated aren?t known bugs in >IoTivity >sources and the Yocto build has been tested successfully by me and others. > >The information I?ve asked for above might possibly help me >identify aspects of your build environment that might be causing >your build to fail. > >Thanks, >-Kishen. > > >On 9/6/15, 11:08 PM, "Raghavendra Kakarla" ><Raghavendra.Kakarla at inedasystems.com> wrote: > >>Hi Kishen, >> >>I updated the yocto to the Fido-1.8 but with this also I get the same >>error. >> >> -> error: 'class HippoMocks::MockRepository' has no member named >>'ExpectCallFuncOverload' >> >> -> error: 'class HippoMocks::MockRepository' has no member named >>'OnCallFuncOverload' >> >>Could you please help me i resolvin g this issue. >> >>Regards, >> >>Raghavendra K. >> >>________________________________________ >>From: Maloor, Kishen <kishen.maloor at intel.com> >>Sent: Saturday, August 29, 2015 2:57 AM >>To: Raghavendra Kakarla; iotivity-dev at lists.iotivity.org >>Subject: Re: [dev] Getting error while building the Iotivity-0.9.2 in >>yocto >> >>Hi, >> >>What version of Yocto are you using? >>FYI, it has been successfully tested with Dizzy (1.7.2) and a 1.8 release >>candidate. >> >>Since this looks like a compile-time error, my first guess is you?re >>using a version >>of Poky that builds an incompatible GCC (with what IoTivity expects i.e.) >>in its >>toolchain. >> >>If thats true, then it would be something that needs to if at all be >>addressed in IoTivity source code, and not in the Yocto recipe. >> >>You could try building your BSP and IoTivity with a newer Yocto release. >>Another solution would be to look inside Hippomocks which would be in >>${S}/extlibs/hippomocks-master to spot and fix the error to make it >>compatible >>with your toolchain. >> >>As such, I?m unable to reproduce the error. >> >>-Kishen. >> >>From: >><iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at >>list >>s >>.iotivity.org>> on behalf of Raghavendra Kakarla >><Raghavendra.Kakarla at inedasystems.com<mailto:Raghavendra.Kakarla at >>inedasys >>t >>ems.com>> >>Date: Thursday, August 27, 2015 at 4:07 AM >>To: >>"iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at >>lists.iotivity.org>" >><iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at >>lists.iotivity.org>> >>Subject: [de -> error: 'class HippoMocks::MockRepository' has no >>member named 'ExpectCallFuncOverload' >> >> -> error: 'class HippoMocks::MockRepository' has no member named >>'OnCallFuncOverload'v] Getting error while building the Iotivity-0.9.2 in >>yocto >> >> >>Hi, >> >> >>I am getting the following error while I am building the Iotivity-0.92 in >>yocto. >> >> >> -> error: 'class HippoMocks::MockRepository' has no member named >>'ExpectCallFuncOverload' >> >> -> error: 'class HippoMocks::MockRepository' has no member named >>'OnCallFuncOverload' >> >> >>Please help me for resolving these issues. >> >> >>Note: Previous versions of Iotivity i.e 0.90 and 0.9.1 are built >>successfully. >> >> >>Thanks in advance. >> >> >>Regards, >> >>Raghavendra K. >
