Dave, Thanks for that, I didn't know install.sh was deprecated. What about build.sh ? They both seem to be included for execution in VagrantFile.
Anyway, if I follow the link you gave me, where should I start from ? If I start with "Build a VPP Package" section, isn't it a duplicate since, I think, the build process (build.sh) is executed during "vagrant up" ? Indeed, all deb packages are already built in /vpp/build-root/ when I logged into it with "vagrant ssh". So, my guess was to directly start with "Install a VPP Package" section, which is actually what is executed with the now-deprecated install.sh. What should I do ? Justin ----- Mail original ----- De: "Dave Wallace" <dwallac...@gmail.com> À: "Justin Iurman" <justin.iur...@ulg.ac.be>, "vpp-dev" <vpp-dev@lists.fd.io> Envoyé: Lundi 16 Octobre 2017 16:06:11 Objet: Re: [vpp-dev] bug/issue notification Justin, install.sh has not been used for many releases and should probably just be removed as it has not been maintained with the updating of the packaging. In order to install VPP in the VM, just follow the recipe in https://wiki.fd.io/view/VPP/Build,_install,_and_test_images Thanks, -daw- On 10/16/2017 07:56 AM, Justin Iurman wrote: > Hey guys, > > Here are two issues I faced while installing/running VPP. It would be great > to fix them. > > 1) Install not executed (at least, it seems that it's the case...) - tested > with current version 18.01 (cloned today) but it's the same with previous > versions too. > > git clone https://gerrit.fd.io/r/vpp > cd vpp/build-root/vagrant > vagrant up > > **waiting during the installation of the VM** > Note: install.sh does not seem to be executed during this process (can't see > related outputs). > > In the VM when logged in with vagrant ssh: > > vvp <-- not found > cd /vpp/build-root/vagrant > ./install.sh <- Permission denied > > First problem: need to manually chmod +x install.sh (maybe that's the reason > why ?). > > Then, execute it again. It finishes but tells me there is a dependency error > (second problem): package python-cffi is not installed. To manually fix it, I > do the following: > > sudo apt-get install python-cffi > sudo apt-get -f install > > After that, install goes fine. Also, note that I've a plugin where a > reference to "vlibsocket/api.h" needs to be removed from plugin.c and > plugin_test.c in order to compile (removed/moved in this new version of VPP > ?). > > 2) This bug seems to be gone since last week with vpp 18.01 (cloned today: > Monday 16 October 2017). But I'll mention it, just in case you didn't hear > about it. When running: "sudo vppctl -s /run/vpp/cli-vpp1.sock create > host-interface name vpp1out", an error was returned (sorry, I don't remember > exactly what was said). And this error was not in earlier versions (around > the 25 September 2017 I'd say). > > Thanks ! > > Justin > _______________________________________________ > 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
