mb78 / dpdk-valgrind

changes to allow use of valgrind-3.10.0+ on a dpdk application (mmap() call fails with -EINVAL otherwise); might help if buffer overflow goes off hugepages
GNU General Public License v2.0
2 stars 3 forks source link

Compilation problem in dpdk-valgrind #1

Open tovivek12 opened 9 years ago

tovivek12 commented 9 years ago

I am facing compilation problem when compilation of dpdk with valgrind patch is done. These are basic errors , not received in DPDK without valgrind patch Target. I am using is x86_64-native-linuxapp-gcc I am facing following errors:- Can you provide the Dpdk release with valgrind fix and without any compilation error ?

In file included from /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:61:0: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_eal.h:76:35: error: âRTE_MAX_LCOREâ undeclared here (not in a function) In file included from /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/generic/rte_spinlock.h:50:0, from /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_spinlock.h:41, from /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_malloc_heap.h:39, from /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_eal_memconfig.h:40, from /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:62: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_lcore.h: In function ârte_lcore_to_socket_idâ: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_lcore.h:115:33: error: parameter âlcore_idâ set but not used [-Werror=unused-but-set-parameter] In file included from /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_rwlock.h:54:0, from /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_eal_memconfig.h:41, from /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:62: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_atomic.h: At top level: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_atomic.h:44:5: error: "RTE_MAX_LCORE" is not defined [-Werror=undef] In file included from /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:62:0: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_eal_memconfig.h:82:27: error: âRTE_MAX_MEMSEGâ undeclared here (not in a function) /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_eal_memconfig.h:83:29: error: âRTE_MAX_MEMZONEâ undeclared here (not in a function) /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_eal_memconfig.h:88:35: error: âRTE_MAX_TAILQâ undeclared here (not in a function) /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_eal_memconfig.h:91:34: error: âRTE_MAX_NUMA_NODESâ undeclared here (not in a function) /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_parse_sysfs_valueâ: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:152:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:152:1: note: each undeclared identifier is reported only once for each function it appears in /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_proc_type_detectâ: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:301:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_parse_socket_memâ: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:397:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:390:9: error: unused variable âargâ [-Werror=unused-variable] /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_parse_argsâ: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:524:30: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_check_mem_on_local_socketâ: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:736:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function ârte_eal_initâ: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:815:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function ârte_eal_lcore_roleâ: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:915:29: error: parameter âlcore_idâ set but not used [-Werror=unused-but-set-parameter] /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:918:1: error: control reaches end of non-void function [-Werror=return-type] /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function ârte_lcore_to_socket_idâ: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_lcore.h:118:1: error: control reaches end of non-void function [-Werror=return-type] cc1: all warnings being treated as errors

mb78 commented 9 years ago

Hi, I could check that the code is compilable on ubuntu 14.04 as per doc/build-sdk-quick.txt: $> make config T=i686-native-linuxapp-gcc $> make

Then you will find ./build/include/rte_config.h with all the missing C macros.

You should also be able to cherry-pick https://github.com/mb78/dpdk-valgrind/commit/e535ab662b959a2a62def2826db526d832e19876 to newer dpdk release, one that I used was 1.7.1.

tovivek12 commented 9 years ago

Hi , which version of dpdk is used for dpdk-valgrind ? let me try your suggestions too and then recompile

mb78 commented 9 years ago

It's 1.7.1, how is it going ?

tovivek12 commented 9 years ago

ok there are problems in compiling sample applications as sample application also needs RTE_MAX_LCORE

/home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_eal.h:76:35: error: âRTE_MAX_LCOREâ undeclared here (not in a function) In file included from /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/examples/l2fwd/main.c:55:0: /home/vivek/dpdk-valgrind-master/dpdk-valgrind-master/x86_64-native-linuxapp-gcc/include/rte_per_lcore.h:54:36: fatal error: exec-env/rte_per_lcore.h: No such file or directory compilation terminated. make[1]: * [main.o] Error 1 make: * [all] Error 2

tovivek12 commented 9 years ago

I removed above compilation errors of sample applications by copying .h files from $RTE_SDK/build/include to path $RTE_SDK/$RTE_TARGET/include but it seems these following libraries are not available to generate executable.

/usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_distributor /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_kni /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_pipeline /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_table /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_port /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_timer /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_hash /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_lpm /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_power /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_acl /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_meter /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_sched /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_kvargs /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_mbuf /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_ip_frag /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lethdev /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_malloc /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_mempool /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_ring /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_eal /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_cmdline /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_cfgfile /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_pmd_bond /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_pmd_vmxnet3_uio /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_pmd_virtio_uio /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_pmd_i40e /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_pmd_ixgbe /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: cannot find -lrte_pmd_e1000

mb78 commented 9 years ago

I merged dpdk 1.8.0, which fixed building process for various config changes in config/common_linuxapp. Can you retry ?

tovivek12 commented 9 years ago

so do i need to download DPDK folder again ?

mb78 commented 9 years ago

Sure, clone my repository again or update existing one

tovivek12 commented 9 years ago

i downloaded new dpdk folder and i try to make using $> make config T=x86_64-native-linuxapp-gcc $> make

make creates error which i did not get when i download the previous version of dpdk

In file included from /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:63:0: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_eal.h:76:35: error: âRTE_MAX_LCOREâ undeclared here (not in a function) In file included from /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/generic/rte_spinlock.h:50:0, from /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_spinlock.h:41, from /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_malloc_heap.h:39, from /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:40, from /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:64: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_lcore.h: In function ârte_lcore_to_socket_idâ: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_lcore.h:153:33: error: parameter âlcore_idâ set but not used [-Werror=unused-but-set-parameter] In file included from /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_rwlock.h:54:0, from /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:41, from /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:64: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_atomic.h: At top level: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_atomic.h:44:5: error: "RTE_MAX_LCORE" is not defined [-Werror=undef] In file included from /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:64:0: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:82:27: error: âRTE_MAX_MEMSEGâ undeclared here (not in a function) /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:83:29: error: âRTE_MAX_MEMZONEâ undeclared here (not in a function) /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:88:35: error: âRTE_MAX_TAILQâ undeclared here (not in a function) /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:91:34: error: âRTE_MAX_NUMA_NODESâ undeclared here (not in a function) /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_parse_sysfs_valueâ: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:154:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:154:1: note: each undeclared identifier is reported only once for each function it appears in /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_proc_type_detectâ: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:303:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_parse_socket_memâ: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:397:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:390:9: error: unused variable âargâ [-Werror=unused-variable] /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_parse_argsâ: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:544:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_check_mem_on_local_socketâ: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:662:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function ârte_eal_initâ: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:747:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function ârte_eal_lcore_roleâ: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:847:29: error: parameter âlcore_idâ set but not used [-Werror=unused-but-set-parameter] /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:850:1: error: control reaches end of non-void function [-Werror=return-type] /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function ârte_lcore_to_socket_idâ: /home/vivek/dpdk-valgrind-master_updated/dpdk-valgrind-master/build/include/rte_lcore.h:156:1: error: control reaches end of non-void function

mb78 commented 9 years ago

Sorry, it seems you have problem with building vanilla dpdk code with procedure from http://dpdk.org/doc/quick-start. You should ask on dpdk maillist or maybe you can send me details:

tovivek12 commented 9 years ago

I am using opensuse 12.1 kernel version 3.1.0-1.2-desktop.

output of mount devtmpfs on /dev type devtmpfs (rw,relatime,size=1853376k,nr_inodes=463344,mode=755) tmpfs on /dev/shm type tmpfs (rw,relatime) tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) /dev/sda2 on / type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=21,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) securityfs on /sys/kernel/security type securityfs (rw,relatime) tmpfs on /var/run type tmpfs (rw,nosuid,nodev,relatime,mode=755) tmpfs on /media type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,relatime,mode=755) /dev/sda3 on /home type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) gvfs-fuse-daemon on /home/user/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)

tovivek12 commented 9 years ago

output of make config T=x86_64-native-linuxapp-gcc; make

== Build scripts == Build scripts/testhost HOSTCC testhost.o HOSTLD testhost INSTALL-HOSTAPP testhost == Build lib == Build lib/librte_eal == Build lib/librte_eal/common SYMLINK-FILE include/generic/rte_atomic.h SYMLINK-FILE include/generic/rte_byteorder.h SYMLINK-FILE include/generic/rte_cycles.h SYMLINK-FILE include/generic/rte_prefetch.h SYMLINK-FILE include/generic/rte_spinlock.h SYMLINK-FILE include/generic/rte_memcpy.h SYMLINK-FILE include/generic/rte_cpuflags.h SYMLINK-FILE include/rte_branch_prediction.h SYMLINK-FILE include/rte_common.h SYMLINK-FILE include/rte_debug.h SYMLINK-FILE include/rte_eal.h SYMLINK-FILE include/rte_errno.h SYMLINK-FILE include/rte_launch.h SYMLINK-FILE include/rte_lcore.h SYMLINK-FILE include/rte_log.h SYMLINK-FILE include/rte_memory.h SYMLINK-FILE include/rte_memzone.h SYMLINK-FILE include/rte_pci.h SYMLINK-FILE include/rte_pci_dev_ids.h SYMLINK-FILE include/rte_per_lcore.h SYMLINK-FILE include/rte_random.h SYMLINK-FILE include/rte_rwlock.h SYMLINK-FILE include/rte_tailq.h SYMLINK-FILE include/rte_interrupts.h SYMLINK-FILE include/rte_alarm.h SYMLINK-FILE include/rte_string_fns.h SYMLINK-FILE include/rte_version.h SYMLINK-FILE include/rte_tailq_elem.h SYMLINK-FILE include/rte_eal_memconfig.h SYMLINK-FILE include/rte_malloc_heap.h SYMLINK-FILE include/rte_hexdump.h SYMLINK-FILE include/rte_devargs.h SYMLINK-FILE include/rte_dev.h SYMLINK-FILE include/rte_common_vect.h SYMLINK-FILE include/rte_pci_dev_feature_defs.h SYMLINK-FILE include/rte_pci_dev_features.h SYMLINK-FILE include/rte_memcpy.h SYMLINK-FILE include/rte_cycles.h SYMLINK-FILE include/rte_spinlock.h SYMLINK-FILE include/rte_atomic_32.h SYMLINK-FILE include/rte_prefetch.h SYMLINK-FILE include/rte_byteorder_32.h SYMLINK-FILE include/rte_atomic_64.h SYMLINK-FILE include/rte_cpuflags.h SYMLINK-FILE include/rte_byteorder_64.h SYMLINK-FILE include/rte_atomic.h SYMLINK-FILE include/rte_byteorder.h == Build lib/librte_eal/linuxapp == Build lib/librte_eal/linuxapp/igb_uio LD /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/build/lib/librte_eal/linuxapp/igb_uio/built-in.o CC [M] /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o (cat /dev/null; echo kernel//home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko;) > /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/build/lib/librte_eal/linuxapp/igb_uio/modules.order Building modules, stage 2. MODPOST 1 modules CC /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o LD [M] /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko INSTALL-MODULE igb_uio.ko == Build lib/librte_eal/linuxapp/eal CC eal.o In file included from /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:63:0: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_eal.h:76:35: error: âRTE_MAX_LCOREâ undeclared here (not in a function) In file included from /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/generic/rte_spinlock.h:50:0, from /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_spinlock.h:41, from /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_malloc_heap.h:39, from /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:40, from /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:64: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_lcore.h: In function ârte_lcore_to_socket_idâ: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_lcore.h:153:33: error: parameter âlcore_idâ set but not used [-Werror=unused-but-set-parameter] In file included from /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_rwlock.h:54:0, from /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:41, from /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:64: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_atomic.h: At top level: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_atomic.h:44:5: error: "RTE_MAX_LCORE" is not defined [-Werror=undef] In file included from /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:64:0: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:82:27: error: âRTE_MAX_MEMSEGâ undeclared here (not in a function) /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:83:29: error: âRTE_MAX_MEMZONEâ undeclared here (not in a function) /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:88:35: error: âRTE_MAX_TAILQâ undeclared here (not in a function) /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_eal_memconfig.h:91:34: error: âRTE_MAX_NUMA_NODESâ undeclared here (not in a function) /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_parse_sysfs_valueâ: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:154:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:154:1: note: each undeclared identifier is reported only once for each function it appears in /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_proc_type_detectâ: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:303:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_parse_socket_memâ: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:397:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:390:9: error: unused variable âargâ [-Werror=unused-variable] /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_parse_argsâ: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:544:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function âeal_check_mem_on_local_socketâ: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:662:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function ârte_eal_initâ: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:747:1: error: âRTE_LOG_LEVELâ undeclared (first use in this function) /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function ârte_eal_lcore_roleâ: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:847:29: error: parameter âlcore_idâ set but not used [-Werror=unused-but-set-parameter] /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c:850:1: error: control reaches end of non-void function [-Werror=return-type] /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/lib/librte_eal/linuxapp/eal/eal.c: In function ârte_lcore_to_socket_idâ: /home/vivek/updated_folder_dpdk/dpdk-valgrind-master/build/include/rte_lcore.h:156:1: error: control reaches end of non-void function [-Werror=return-type] cc1: all warnings being treated as errors

tovivek12 commented 9 years ago

linux-vlu1:/home/vivek/updated_folder_dpdk/dpdk-valgrind-master # find -type f -exec ls -ld "{}" find: missing argument to `-exec'

tovivek12 commented 9 years ago

when i used make config T=x86_64-native-linuxapp-gcc make on previous version of dpdk on which sample applications executable was not generated, then DPDK was installed