A few more details: this is race condition in parallel execution of “make 
install” targets.
I am aware of the problem, but for me it was hard to troubleshoot as it is not 
happening
in my system, and so far I noticed it only occasionaly in verify jobs.

I think it was caused by:

libvppinfradir = ${libdir}
libvppinfra_LTLIBRARIES = libvppinfra.la

And is now fixed with:

lib_LTLIBRARIES += libvppinfra.la


Basically by having 2 LTLIBRARIES groups, we were allowing Make to install them 
in parallel.
As we are relinking libs during install, it was happening that that lib was not 
there when
it was needed.

Let me know if it works now, if not I have some other ideas what we can do…

Thanks,

Damjan


> On 12 Jan 2017, at 23:59, Damjan Marion <dmarion.li...@gmail.com> wrote:
> 
> 
> Hi Jon,
> 
> Do you see this issue with latest master, taken today?
> 
> Thanks,
> 
> Damjan
> 
> 
> On 11 Jan 2017, at 22:59, 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

Reply via email to