On Wed, Jun 01, 2016 at 08:31:26PM +0200, Mauricio Vásquez wrote:
> Hi Ben,
>
> On Wed, Jun 1, 2016 at 7:38 PM, Ben Pfaff wrote:
>
> > On Wed, Jun 01, 2016 at 06:48:07PM +0200, Mauricio Vasquez B wrote:
> > > when an empty path is given to the --with-dpdk option
> > > (--with-dpdk="" or --width-
Hi Ben,
On Wed, Jun 1, 2016 at 7:38 PM, Ben Pfaff wrote:
> On Wed, Jun 01, 2016 at 06:48:07PM +0200, Mauricio Vasquez B wrote:
> > when an empty path is given to the --with-dpdk option
> > (--with-dpdk="" or --width-dpdk=$NON_SET_ENV_VARIABLE) the configure
> > script does not show any error and
On Wed, Jun 01, 2016 at 06:48:07PM +0200, Mauricio Vasquez B wrote:
> when an empty path is given to the --with-dpdk option
> (--with-dpdk="" or --width-dpdk=$NON_SET_ENV_VARIABLE) the configure
> script does not show any error and configures OvS without DPDK support,
> this can create some confusi
On Wed, Jun 01, 2016 at 06:48:07PM +0200, Mauricio Vasquez B wrote:
> when an empty path is given to the --with-dpdk option
> (--with-dpdk="" or --width-dpdk=$NON_SET_ENV_VARIABLE) the configure
> script does not show any error and configures OvS without DPDK support,
> this can create some confusi
when an empty path is given to the --with-dpdk option
(--with-dpdk="" or --width-dpdk=$NON_SET_ENV_VARIABLE) the configure
script does not show any error and configures OvS without DPDK support,
this can create some confusion.
This patch modifies that behavior showing an explicity error in that ca
