I have seen this. I was compiling in a VM with 5 CPUs. I isolate CPUs 1-4
from Linux via kernel cmdline arg isocpu. When compiling with 1 CPU I saw
the issue every time. Removed isocpu and compiled with 5 CPUs everything
worked.

Billy McFall

On Mon, Mar 6, 2017 at 3:42 PM, Jon Loeliger <j...@netgate.com> wrote:

> Guys,
>
> I am in the process of setting up a CI engine here.  (Whee!)
> This is on an entirely new machine with a new number of CPUs, etc.
> What I'm noticing is that every other build or so fails.  And it seems
> to be for lack of a -lpneum each time it fails.  But sometimes it all
> builds properly too.
>
> What I'm thinking is that we have another missing dependency in
> the Makefile somewhere that is allowing an out-of-order reference
> to the pneum library prior to it really being ready.  (We had a problem
> like this a few months ago too.  Blah.)
>
> Anyone else seen anything like this?  Am I out in the weeds?
>
> Logs from around the build failure below...
>
> Thanks
> jdl
>
>
>
> mkdir -p 
> /var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp/lib/python2.7/site-packages;
>                                          \
> mkdir -p 
> /var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp/lib64/python2.7/site-packages;
>                                                \
> PYTHONUSERBASE=/var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp
>                                         \
> python setup.py build_ext -L 
> /var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp/lib64
>                             \
> -I 
> /var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp/include/
>  install --user
>  /bin/mkdir -p 
> '/var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp/lib64'
>  /bin/mkdir -p 
> '/var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp/include'
>  /bin/sh ../../libtool --quiet  --mode=install /bin/install -c   libpneum.la 
> '/var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp/lib64'
>  /bin/mkdir -p 
> '/var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp/include/pneum'
>  /bin/install -c -m 644  
> /var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-data/../src/vpp-api/python/pneum/pneum.h
>  
> '/var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp/include/pneum'
> libtool: install: warning: relinking `libpneum.la'
> running build_ext
> building 'vpp_api' extension
> creating build
> creating build/temp.linux-x86_64-2.7
> creating build/temp.linux-x86_64-2.7/vpp_papi
> gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 
> -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 
> -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv 
> -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions 
> -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 
> -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC 
> -I/var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp/include/
>  -I/usr/include/python2.7 -c vpp_papi/pneum_wrap.c -o 
> build/temp.linux-x86_64-2.7/vpp_papi/pneum_wrap.o
> creating build/lib.linux-x86_64-2.7
> gcc -pthread -shared -Wl,-z,relro 
> build/temp.linux-x86_64-2.7/vpp_papi/pneum_wrap.o 
> -L/var/lib/jenkins/workspace/build-ngr-rpm/build_root/BUILD/vpp/build-root/install-vpp-native/vpp/lib64
>  -L. -lpneum -lpython2.7 -o build/lib.linux-x86_64-2.7/vpp_api.so
> /bin/ld: cannot find -lpneum
> collect2: error: ld returned 1 exit status
> error: command 'gcc' failed with exit status 1
>
>
>
>
> _______________________________________________
> 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