Hi Numan,
The libopenvswitch.so is indeed being generated if i do not invoke the
"setup.py build" in the do_compile_append() function (of the OVS bitbake) i
mentioned in my email. However i see the C JSON parser extension doesnt get
compiled. The "*import ovs._json*" fails on the target..This led to me to
believe that the C JSON parser compilation doesnt happen by default and has
to be explicitly enabled, after which i see the compilation issue.
As the compilation error seems to indicate a problem with finding the
"include" path/directory, i thought it might be somehting to do with how we
provide the include dir paths in the automake or the setup.py
(setuptools.Extension()). But no matter what i try, i cant seem to get
beyond this..
Thanks,
On Thu, Jun 13, 2019 at 11:41 AM Numan Siddique <nusid...@redhat.com> wrote:
>
>
> On Thu, Jun 13, 2019 at 8:17 AM nitish nagesh <nagesh.nit...@gmail.com>
> wrote:
>
>> Thanks Ben.
>>
>> Guys, any other recommendations, please help me out here.
>>
>
> I think you may have to compile openvswitch too with shared library option
> so that libopenvswitch.so is generated.
> I am not sure if this would help, but the openvswitch fedora spec file
> does it this way -
>
> https://src.fedoraproject.org/rpms/openvswitch/blob/master/f/openvswitch.spec#_326
>
>
> Thanks
> Numan
>
>
>> Thanks,
>>
>> On Wed, Jun 12, 2019 at 10:48 PM Ben Pfaff <b...@ovn.org> wrote:
>>
>>> On Wed, Jun 12, 2019 at 09:41:03PM +0530, nitish nagesh wrote:
>>> > | arm-cnos-linux-gnueabi-gcc -march=armv7-a
>>> > --sysroot=/build/tmp/sysroots/switch -DNDEBUG -g -O3 -Wall
>>> > -Wstrict-prototypes -O2 -pipe -ggdb3 -feliminate-unused-debug-types
>>> >
>>> -fdebug-prefix-map=/build/tmp/work/armv7a-cnos-linux-gnueabi/ops-openvswitch/1.0-r0_switch=/usr/src/debug/ops-openvswitch/1.0-r0_switch
>>> > -fdebug-prefix-map=/build/tmp/sysroots/x86_64-linux=
>>> > -fdebug-prefix-map=/build/tmp/sysroots/switch= -DOPS -fPIC -INone -I
>>> > /build/tmp/sysroots/dover/usr/include/python2.7 -c ovs/_json.c -o
>>> > build/temp.linux-x86_64-2.7/ovs/_json.o
>>> >
>>> > | ovs/_json.c:2:30: fatal error: openvswitch/json.h: No such file or
>>> > directory
>>> >
>>> >
>>> >
>>> > I tried several option, to the best of my knowledge, to pass he
>>> include
>>> > path to the build system (using include_dirs in setup.py, through
>>> > automake.mk etc). But I can’t seem to get my head around this. I am a
>>> > novice to yocto & autotools. I am starting to doubt if the approach I
>>> am
>>> > following is even correct?
>>>
>>> I don't think that the OVS use of Python is very special. My guess is
>>> that your question can be answered by looking in some more generic place
>>> for advice on (cross?)compiling Python binary modules.
>>>
>>> I don't have experience in this particular area, so I'm not able to
>>> offer more useful advice than that. Maybe someone else will speak up,
>>> if we're lucky.
>>>
>> _______________________________________________
>> discuss mailing list
>> disc...@openvswitch.org
>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>>
>
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
