Where is that library located, or is it entirely missing? If you find it, how about making a symbolic link?
Thanks… Dave From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Burt Silverman Sent: Friday, August 11, 2017 3:26 PM To: Marco Varlese <marco.varl...@suse.com> Cc: vpp-dev <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] Issues building latest master After updating my nasm, I am seeing the very same problem Marco is seeing. On openSUSE 42.3. Not seen on CentOS 7. Not seen on my VyOS system. Burt On Fri, Aug 11, 2017 at 10:36 AM, Marco Varlese <marco.varl...@suse.com<mailto:marco.varl...@suse.com>> wrote: Hi, I am having troubles building the latest code off the master branch. The commands I always use are: > make bootstrap > make build I get this error: cp: cannot stat '/home/marco/vpp/build-root/build-vpp_debug-native/dpdk/isa- l_crypto-2.18.0/install/lib/libisal_crypto.a': No such file or directory I noticed that once the compilation of DPDK completes the libraries - as suggested by the build process itself - are placed at: /home/marco/vpp/build-root/build-vpp_debug-native/dpdk/isa-l_crypto- 2.18.0/install/lib64 So it looks like somewhere the build system is using "lib64" and in another place just "lib". I wonder if something has changed and - in that case - what shall I do? Also, I noticed that setting the vpp_uses_dpdk_cryptodev_sw = no in build- date/platforms/vpp.mk<http://vpp.mk> has no effect (e.g. whether yes or no the build process still builds the crypto stuff from DPDK). Is this a known behaviour? Cheers, Marco _______________________________________________ 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
