On 14/08/2017 09:11, Marco Varlese wrote:
Hi Sergio,
I tried on a different machine and I got this:
libdir: ${exec_prefix}/lib64
That confirms that ./configure is setting a different libdir in OpenSUSE
than RHEL/Ubuntu.
I'll fix that by forcing libdir to always be ${exec_prefix}/lib
Thanks,
Sergio
Thanks,
Marco
Marco Varlese 08/14/17 10:04 AM >>>
Sergio Gonzalez Monroy <sergio.gonzalez.mon...@intel.com> 08/14/17 9:17 AM >>>
Hi,
So I gather that:
1. DPDK and the SW crypto libraries are building without errors
2. Only OpenSUSE displays this behavior.
Only thing I can think of is that configure has different default libdir
directory in OpenSUSE?
Could you show the output of the following command:
grep "libdir:"
build-root/build-vpp_debug-native/dpdk/isa-l_crypto-2.18.0/config.log
mvarlese@linux-yk3w:~/repos/vpp> grep "libdir:"
build-root/build-vpp_debug-native/dpdk/isa-l_crypto-2.18.0/config.log
grep: build-root/build-vpp_debug-native/dpdk/isa-l_crypto-2.18.0/config.log: No
such file or directory
Regarding the option vpp_uses_dpdk_cryptodev_sw=yes, it is indeed not
used anymore but I obviously missed some cleanup.
Thanks,
Sergio
On 11/08/2017 20:25, Burt Silverman wrote:
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
<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
marco@linux-3s68:~/vpp> grep "libdir:"
build-root/build-vpp_debug-native/dpdk/isa-l_crypto-2.18.0/config.log
libdir: ${exec_prefix}/lib64
marco@linux-3s68:~/vpp> grep "libdir:"
build-root/build-vpp_debug-native/dpdk/isa-l_crypto-2.18.0/config.log
libdir: ${exec_prefix}/lib64
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
