On Mon, Nov 6, 2017 at 4:09 PM, Florin Coras <fcoras.li...@gmail.com> wrote:

> Hi Lori,
>
> backup
> git clean -fdx
> make bootstrap
> make build
>
> Any luck?
>

Yes, and that's weird... the fresh git clone should be the same as the
result of `git clean -dfx`. The only reasonable explanation I have is that
I tried the boostrap before installing all deps, so maybe that put the tree
into a weird state...?

Thanks for the help, I should have tried git clean it myself :)

-Lori


>
> Florin
>
> On Nov 6, 2017, at 4:17 AM, Lori Jakab <lorand.jakab+f...@gmail.com>
> wrote:
>
> Hi,
>
> I see the exact same issue that is reported in a previous thread [0],
> which didn't have a solution. I wonder if anyone has more insight now.
>
> I did not use Vagrant to set up a VM with the build environment. On an
> Ubuntu 16.04 VM I clone VPP latest master, do a `make install-dep` and then
> a `make bootstrap`. This is what I get:
>
> [...]
> checking for LIBRTE_PMD_AESNI_MB in rte_config.h... no
> checking for LIBRTE_PMD_AESNI_GCM in rte_config.h... no
> checking for RTE_VERSION 17.02/17.05 in rte_version.h... no
> checking for LIBRTE_MLX4_PMD in rte_config.h... no
> checking for LIBRTE_MLX5_PMD in rte_config.h... no
> /home/vagrant/vpp/build-root/../src/configure: line 18206: syntax error
> near unexpected token `g2,'
> /home/vagrant/vpp/build-root/../src/configure: line 18206: `
>  PKG_CHECK_MODULES(g2, gtk+-2.0)'
> Makefile:635: recipe for target 'tools-configure' failed
> make[1]: *** [tools-configure] Error 2
> make[1]: Leaving directory '/home/vagrant/vpp/build-root'
> Makefile:226: recipe for target '/home/vagrant/vpp/build-root/.bootstrap.ok'
> failed
> make: *** [/home/vagrant/vpp/build-root/.bootstrap.ok] Error 2
>
> No idea what package may I be missing.
>
> -Lori
>
> [0] https://lists.fd.io/pipermail/vpp-dev/2017-March/004543.html
> _______________________________________________
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
>
>
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Reply via email to