With the posted steps, I was able to build CentOS on a clean VPP sandbox.
Unicast me if it is still not working. Here is my system info:
   CentOS Linux release 7.2.1511
   3.10.0-327.13.1.el7.x86_64

Billy

On Thu, Jan 12, 2017 at 7:51 AM, Billy McFall <bmcf...@redhat.com> wrote:

> I build on CentOS and Fedora regularly, though it has been Fedora more
> recently. I haven't seen it bail on vppifra, but I will go kick off a fresh
> sandbox on CentOS right now. In the meantime, here are my steps on a fresh
> sandbox:
>    cd vpp;  make install-dep;  make bootstrap;  make build-release;  make
> pkg-rpm
>
> After some git activity, such as pushing a patch, the .version file
> becomes stale and needs to be regenerated. So I run:
>    cd vpp;  make wipe;
>
> I'll let you know what I find on a fresh build.
>
> Billy McFall
>
> On Wed, Jan 11, 2017 at 6:29 PM, Dave Barach (dbarach) <dbar...@cisco.com>
> wrote:
>
>> Here’s what I do when switching branches:
>>
>>
>>
>> $ cd build-root
>>
>> $ make distclean
>>
>> $ cd ../
>>
>> $ git clean -fx
>>
>> $ cd build-root
>>
>> $ ./bootstrap.sh
>>
>> $ # build should work
>>
>>
>>
>> HTH… Dave
>>
>>
>>
>> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
>> Behalf Of *Burt Silverman
>> *Sent:* Wednesday, January 11, 2017 5:46 PM
>> *To:* Jon Loeliger <j...@netgate.com>
>> *Cc:* vpp-dev <vpp-dev@lists.fd.io>
>> *Subject:* Re: [vpp-dev] VPP Build Bombing Out on libsvm.la?
>>
>>
>>
>> I don't have a great answer, but this is something I would try.
>>
>> If you have a clean git repository, with no local uncommitted
>> modifications (if you have any, then stash them so they won't be lost), I
>> would try from the top of the tree:
>>
>> $ rm -rf *  #make sure you do not use .*
>>
>> $ git checkout .
>>
>> Now try your entire build sequence again.
>>
>> The reasoning is: if you checkout an older level AND build AND then
>> switch to master, sometimes some crud is left around. Although one would
>> expect that crud to be harmless, it cannot hurt for you to do an extra
>> check. More sophisticated debugging can be done if the problem does not get
>> solved this simple(ton) way.
>>
>> Burt
>>
>>
>>
>> On Wed, Jan 11, 2017 at 4:59 PM, Jon Loeliger <j...@netgate.com> wrote:
>>
>> Folks,
>>
>>
>>
>> I'm staring at some VPP builds on a fresh CentOS system.
>>
>> I've installed all the "install-deps", and get pretty far into the
>>
>> build before it wedges.  I see warnings like this:
>>
>>
>>
>>  /bin/sh ./libtool   --mode=install /usr/bin/install -c   libsvm.la
>> libsvmdb.la libvlib.la libvlibapi.la libvlibmemory.la
>> libvlibmemoryclient.la libvlibsocket.la libvatplugin.la
>> '/home/jdl/ngr-rpms/build_root/BUILD/vpp/build-root/install-
>> vpp-native/vpp/lib64'
>>
>> PLUGIN CFG vpp_plugin_configure
>>
>> libtool: install: warning: relinking `libsvm.la'
>>
>>
>>
>> I don't know if that is important misbehavior or normal behavior.
>>
>>
>>
>> Ultimately, most of the builds quit grousing about a missing libvppinfra:
>>
>>
>>
>> /usr/bin/ld: cannot find -lvppinfra
>>
>> collect2: error: ld returned 1 exit status
>>
>> libtool: install: error: relink `libsvm.la' with the above command
>> before installing it
>>
>> make[6]: *** [install-libLTLIBRARIES] Error 1
>>
>> make[6]: *** Waiting for unfinished jobs....
>>
>>
>>
>> Not sure which real target issued that loveliness due to some "make -j"
>>
>> parallelism in the mix.  Might be the relinking of libvnet.la.
>>
>>
>>
>> I am able to build VPP on an entirely different system though.
>>
>> So it seems like there is some variability in its success rate.
>>
>>
>>
>> Is it possible that there is a missing dependency and the "-j" is
>>
>> effectively causing it to want libvppinfra before it is available?
>>
>>
>>
>> Ideas or suggestions?
>>
>>
>> Thanks,
>>
>> jdl
>>
>>
>>
>>
>> _______________________________________________
>> 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

Reply via email to