[vpp-dev] syntax error near unexpected token `g2,'

2017-11-06 Thread Lori Jakab
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

Re: [vpp-dev] syntax error near unexpected token `g2,'

2017-11-06 Thread Florin Coras
Hi Lori, 

backup
git clean -fdx
make bootstrap 
make build

Any luck?

Florin

> On Nov 6, 2017, at 4:17 AM, Lori Jakab  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

Re: [vpp-dev] syntax error near unexpected token `g2,'

2017-11-06 Thread Lori Jakab
On Mon, Nov 6, 2017 at 4:09 PM, Florin Coras  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 
> 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

Re: [vpp-dev] syntax error near unexpected token `g2,'

2017-11-06 Thread Burt Silverman
Yes, it is a weird one. I am sure it has happened to me at least once, and
I gave up trying to analyze it. We can say that there is only one instance
of PKG_CHECK_MODULES in src/configure.ac. And often these macros like to
see plenty of '[' and ']' characters, and those are not present (you can
compare against other macros in that file.) That is as far as I will take
it, since it is a nuisance to re-create the problem.

Burt

On Mon, Nov 6, 2017 at 10:20 AM, Lori Jakab 
wrote:

> On Mon, Nov 6, 2017 at 4:09 PM, Florin Coras 
> 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 
>> 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
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev