Maybe you need to do some visual inspection during the build to check that what you think is being built is indeed being built and linked. Possibly you might
[V=1] make build-release > build.log 2>&1 and look in build.log. Also manually examine timestamps on relevant files along with that. Until you know for sure what works and what does not. My build does not generate new kernel modules; I defer to someone who knows more about this topic. Burt On Thu, Mar 15, 2018 at 6:34 AM, xulang <xlang...@163.com> wrote: > Hi, > I changed DPDK_BUILD_DIR ?= $(CURDIR)/dpdk-17.02 and the > file "rte_eth_bond_pmd.c" under this folder. > I also changed dpdk Makefile like this: > $(B)/.extract.ok: $(B)/.download.ok > #@echo --- extracting $(DPDK_TARBALL) --- > #@tar --directory $(B) --extract --file $(CURDIR)/$(DPDK_TARBALL) > #@cp ./dpdk-17.02/drivers/net/bonding/rte_eth_bond_pmd.c > ./_build/dpdk-17.02/drivers/net/bonding/ > > Then I insert the new igb_uio.ko, but it still does not work. > The compile procedure of VPP and DPDK are independent from each other, am > I right? > I hope to hearing from you. > > > Regards, > Xulang > > > > > > > >
