[ovs-discuss] Compiling OVS

[Sadia Bashir]

Hello Haleema,

I also made changes to OVS datapath, userspace and OVSDB processes for my
dissertation and used instructions given here
<https://github.com/openvswitch/ovs/blob/master/utilities/ovs-dev.py> for
this purpose.

Hope it helps.

On Thu, Jan 7, 2016 at 10:57 PM, Haleema Sadia <haleema.s.mahmood at gmail.com>
wrote:

> And when I do it in the root folder, sudo make returns the following error:
>
> perl: warning: Setting locale failed.
>
> perl: warning: Please check that your locale settings:
>
> LANGUAGE = "en_US:",
>
> LC_ALL = (unset),
>
> LC_CTYPE = "UTF-8",
>
> LANG = "en_US.UTF-8"
>
>     are supported and installed on your system.
>
> perl: warning: Falling back to the standard locale ("C").
>
> automake: error: cannot open < debian/automake.mk: No such file or
> directory
>
> autoreconf: automake failed with exit status: 1
>
> On Thu, Jan 7, 2016 at 10:46 PM, Haleema Sadia <
> haleema.s.mahmood at gmail.com> wrote:
>
>> I did that in the ofproto folder since this is where I am making my
>> changes and there is an automake.mk file in it, but it gives me the
>> following error:
>>
>> make: *** No targets specified and no makefile found.  Stop.
>>
>>
>>
>>
>> On Thu, Jan 7, 2016 at 10:44 PM, Justin Pettit <jpettit at ovn.org> wrote:
>>
>>>
>>> > On Jan 7, 2016, at 6:33 AM, Haleema Sadia <haleema.s.mahmood at gmail.com>
>>> wrote:
>>> >
>>> > Hi,
>>> >
>>> > I have made some changes in the OVS source code. Can somebody please
>>> tell me how to 'make' the .c files it after I have made the changes.
>>>
>>> Assuming you followed the instructions in INSTALL.md, it should just
>>> work when you run "make".
>>>
>>> --Justin
>>>
>>>
>>>
>>>
>>>
>>
>
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss
>
>


--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20160107/aee64ca6/attachment-0002.html>