Tomas,

Just another data point for you/whomever its not specific to forking..
If you do a shallow clone  —depth=1 you will get the same error on build…

Ed




On Jun 2, 2017, at 12:49 AM, Tomas Brännström 
<tomas.a.brannst...@tieto.com<mailto:tomas.a.brannst...@tieto.com>> wrote:

No it's the same :-(

One thing though: when I get these errors I clone from a fork of the vpp repo 
that we made. Is there some kind of git-hook that creates these version 
files/update the .deb files with a version when cloning from the main vpp 
gerrit repository, that might not fire when cloning from a fork?

/Tomas

On 1 June 2017 at 19:02, Florin Coras 
<fcoras.li...@gmail.com<mailto:fcoras.li...@gmail.com>> wrote:
Hi Tomas,

That sure is weird.

(backup everything that’s not in git)
git clean -fdx
make bootstrap
make build

Do you still see the issue?

HTH,
Florin

On Jun 1, 2017, at 6:18 AM, Tomas Brännström 
<tomas.a.brannst...@tieto.com<mailto:tomas.a.brannst...@tieto.com>> wrote:

Hi
I'm getting build errors when trying to build a recent commit on the master 
branch:

/home/ubuntu/git/vpp/build-data/../src/vnet/tcp/builtin_client.c:25:29: fatal 
error: vpp/app/version.h: No such file or directory
 #include <vpp/app/version.h>
                             ^
compilation terminated.

I'm building using the "extras/vagrant/build.sh" script (or 
"build-root/vagrant/build.sh" in slightly earlier versions). What's strange 
here is that I built it successfully on the exact same commit yesterday on 
another machine. The commit in question is 
79ea7ec3b3c04d334a21107818c64d70c42b99ae but I tried on the latest master as 
well.

Also, I tried to build an earlier version (git tag v17.07-rc0) and got another 
error, where the .deb files could not be built  because the "version" was 
missing. I don't have the exact printout though.

Am I missing something here? I'm trying to build in an ubuntu trusty server 
install, and it has worked before.

/Tomas

_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
https://lists.fd.io/mailman/listinfo/vpp-dev


_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io<mailto: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