[ovs-discuss] building ovs for userspace

[Joe Stringer]

The userspace install docs describe how:

https://github.com/openvswitch/ovs/blob/master/INSTALL.userspace


On 10 July 2014 14:27, Rod N. Melton <rnm at pobox.com> wrote:

>
>
> then how do i install OVS so that it runs in userspace and MPLS is
> available?
>
>
>          From: Ben Pfaff <> To: "Rod N. Melton" <> Cc: ovs <
> discuss at openvswitch.org>
>
>
>
> There is no option to build for userspace. It is always supported.
> On Jul 9, 2014 6:57 PM, "Rod N. Melton" <rnm at pobox.com> wrote:
>
>>
>>
>> i am using ubuntu 14.04 in virtualbox.
>>
>> I am trying to build openvswitch for userspace (so that I can use MPLS).
>>
>> when i get ovs source from:
>>
>> 1.)git clone https://github.com/openvswitch/ovs.git OR from
>> http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=snapshot;sf=tgz;h=HEAD
>> ,
>>
>> boot.sh gets the following error:
>>
>> configure.ac:43: error: possibly undefined macro: LT_INIT
>>       If this token and others are legitimate, please use m4_pattern_allow.
>>
>>
>>       See the Autoconf documentation.
>> autoreconf: /usr/bin/autoconf failed with exit status: 1
>>
>> 2.) when i get source from:
>> http://openvswitch.org/releases/openvswitch-2.1.2.tar.gz ,
>>
>> the boot.sh completes normally. I run ./configure which seems to complete
>> normally but
>>
>> it does not give me the option to build for userspace. Is there a special
>> flag to pass to configure or make
>>
>> which specifies build for putting the switch in userspace?
>>
>>
>>
>> thx, Rod
>>
>>
>>
>>
>> _______________________________________________
>> discuss mailing list
>> discuss at openvswitch.org
>> http://openvswitch.org/mailman/listinfo/discuss
>>
>>
>
> _______________________________________________
> 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/20140710/578959e0/attachment-0002.html>