Re: [vpp-dev] Build errors

roughly twice the number of tools to get the same result. > > FWIW... Dave > > -----Original Message- > From: vpp-dev@lists.fd.io On Behalf Of carlito nueno > Sent: Friday, August 16, 2019 12:58 AM > To: Carlito Nueno > Cc: vpp-dev@lists.fd.io > Subject: Re: [vpp-dev] B

Re: [vpp-dev] Build errors

. FWIW... Dave -Original Message- From: vpp-dev@lists.fd.io On Behalf Of carlito nueno Sent: Friday, August 16, 2019 12:58 AM To: Carlito Nueno Cc: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] Build errors Hi all, I think I found the problem. fatal: ambiguous argument 'v1.19-rc0..': unknown

Re: [vpp-dev] Build errors

Hi all, I think I found the problem. fatal: ambiguous argument 'v1.19-rc0..': unknown revision or path not in the working tree. Here are steps I did: - I forked `stable/1908` branch and added some code to it. - Now my branch is `test-stable/1908` - I tagged my branch with `v1.19.08`. - I pushed

Re: [vpp-dev] Build errors

I am getting the same error with: build-root/vagrant/build.sh On Thu, Aug 15, 2019 at 5:21 PM carlito nueno via Lists.Fd.Io wrote: > > Hi all, > > I am following this guide to build VPP: > https://wiki.fd.io/view/VPP/Pulling,_Building,_Running,_Hacking_and_Pushing_VPP_Code > > I added a patch to

[vpp-dev] Build errors

Hi all, I am following this guide to build VPP: https://wiki.fd.io/view/VPP/Pulling,_Building,_Running,_Hacking_and_Pushing_VPP_Code I added a patch to stable/1908 branch using ubuntu 18.04LTS running as ROOT user I followed these steps: apt-get update apt-get install build-essential make

Re: [vpp-dev] build errors on CenOS 7.5

Neale, You are so nice to let me know about it. Thanks a lot. Zhiyong From: Neale Ranns (nranns) [mailto:nra...@cisco.com] Sent: Friday, December 21, 2018 3:47 PM To: Yang, Zhiyong ; Paul Vinciguerra Cc: Ole Troan ; vpp-dev@lists.fd.io; Damjan Marion Subject: Re: [vpp-dev] build errors

Re: [vpp-dev] build errors on CenOS 7.5

egards Zhiyong From: Paul Vinciguerra [mailto:pvi...@vinciconsulting.com] Sent: Thursday, December 20, 2018 11:55 PM To: Neale Ranns (nranns) Cc: Ole Troan ; Yang, Zhiyong ; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] build errors on CenOS 7.5 Sure. Revert it. If that's the case, I need to l

Re: [vpp-dev] build errors on CenOS 7.5

[mailto:pvi...@vinciconsulting.com] Sent: Thursday, December 20, 2018 11:55 PM To: Neale Ranns (nranns) Cc: Ole Troan ; Yang, Zhiyong ; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] build errors on CenOS 7.5 Sure. Revert it. If that's the case, I need to look at why make wipe is missing it. On Thu, Dec 20

Re: [vpp-dev] build errors on CenOS 7.5

jeudi 20 décembre 2018 à 16:03 > *À : *"Neale Ranns (nranns)" > *Cc : *Ole Troan , Zhiyong Yang < > zhiyong.y...@intel.com>, "vpp-dev@lists.fd.io" > *Objet : *Re: [vpp-dev] build errors on CenOS 7.5 > > > > Up until two days ago, make wipe

Re: [vpp-dev] build errors on CenOS 7.5

: Paul Vinciguerra Date : jeudi 20 décembre 2018 à 16:03 À : "Neale Ranns (nranns)" Cc : Ole Troan , Zhiyong Yang , "vpp-dev@lists.fd.io" Objet : Re: [vpp-dev] build errors on CenOS 7.5 Up until two days ago, make wipe did not clean out .api.json files. It had to be

Re: [vpp-dev] build errors on CenOS 7.5

“struct _vl_api_mac_address” > > > > do you need a ‘make wipe’ to regenerate the files derived from the gbp.api > ? > > > > /neale > > > > > > *De : * au nom de Ole Troan > *Date : *jeudi 20 décembre 2018 à 11:07 > *À : *Zhiyong Yang >

Re: [vpp-dev] build errors on CenOS 7.5

neale De : au nom de "Neale Ranns via Lists.Fd.Io" Répondre à : "Neale Ranns (nranns)" Date : jeudi 20 décembre 2018 à 13:33 À : Ole Troan , Zhiyong Yang Cc : "vpp-dev@lists.fd.io" Objet : Re: [vpp-dev] build errors on CenOS 7.5 /root/zhiyong/vpp/src/vnet/e

Re: [vpp-dev] build errors on CenOS 7.5

is not of type “struct _vl_api_mac_address” do you need a ‘make wipe’ to regenerate the files derived from the gbp.api ? /neale De : au nom de Ole Troan Date : jeudi 20 décembre 2018 à 11:07 À : Zhiyong Yang Cc : "vpp-dev@lists.fd.io" Objet : Re: [vpp-dev] build errors on CenOS 7.5 Hi,

Re: [vpp-dev] build errors on CenOS 7.5

@lists.fd.io Subject: Re: [vpp-dev] build errors on CenOS 7.5 Ole, Damjan, It works well now. Thank you guys. I believe there should be no problem for other OSes as well. ☺ Regards Zhiyong From: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> [mailto:vpp-dev@lists.fd.io] On

Re: [vpp-dev] build errors on CenOS 7.5

@lists.fd.io Subject: Re: [vpp-dev] build errors on CenOS 7.5 Hi, Paul also noticed that, and provided a fix in https://gerrit.fd.io/r/#/c/16562/ Just merged. Can you confirm that fixes the issue? Also which compiler and version do you use? Cheers Ole -=-=-=-=-=-=-=-=-=-=-=- Links: You receive

Re: [vpp-dev] build errors on CenOS 7.5

> On 20 Dec 2018, at 11:04, Zhiyong Yang wrote: > > Hi VPP guys, > > Could you notice this building errors on CentOs as below? > Could anybody help fix it? > > Regards > Zhiyong > Does https://gerrit.fd.io/r/#/c/16562/ helps?

[vpp-dev] build errors on CenOS 7.5

Hi VPP guys, Could you notice this building errors on CentOs as below? Could anybody help fix it? Regards Zhiyong Prefix path : /opt/vpp/external/x86_64;/root/zhiyong/vpp/build-root/install-vpp-native/external Install prefix :

Re: [vpp-dev] Build Errors

Long, but below are the three types of errors I hit. I am writing a Jira now and will submit a patch to fix them later today. *1) There is a semi-colon at the end of the if statement. Fix was merged yesterday.* *vnet/vnet/fib/fib_entry_src_interface.c* starting at line 54 if

Re: [vpp-dev] Build Errors

Hi Bill, Error output copy/pasted here or to pastebin will be a good start. Thanks, Damjan > On 13 Oct 2016, at 15:55, Billy McFall wrote: > > I am getting build errors from a newly created sandbox based off master. The > build errors are coming from a patch submitted 3

[vpp-dev] Build Errors

I am getting build errors from a newly created sandbox based off master. The build errors are coming from a patch submitted 3 weeks ago. One of the errors was fixed yesterday as a Coverity warning. So my question is, what is different on my system that these are treated as errors but I haven't