Hey Brian,

I believe it fetches it again because the file doesn't match the hash string 
present in one of the files inside the dpdk directory. At least that was the 
issue I faced building for Mellanox cards ages ago. You could also specify that 
it uses an external DPDK source.

Sent from ny phone




On Tue, Dec 18, 2018 at 5:20 AM +0100, "Brian Dickson" 
<brian.peter.dick...@gmail.com<mailto:brian.peter.dick...@gmail.com>> wrote:

Hi, VPP folks,

I am trying to add in support for a new card/driver.

The info on the DPDK website says the drivers I have should work fine.

Thus, the only issue is adding in the correct manufacturer/device IDs into the 
init.c file:

src/plugins/dpdk/device/init.c


I edit the file (one-line change), put it back into the .tar.xz file, put it 
where it should be being picked up (in build-root or so I believe), and it gets 
blown away.


It always seems to want to pull everything from git regardless of the presence 
of the right tar.xz file in build-root, pointed to by the vpp-latest symbolic 
link.


I am using "make pkg-rpm" as the command to rebuild things from the main vpp 
source root (parent of build-root).


What am I doing wrong?


Where should I be rebuilding this?

What command should I use?

Or what make target?

In what directory?


Thanks in advance.


Brian


P.S. I already spent a lot of time chasing a red herring. Does someone want to 
explain to me the purpose of the "sed -e s/-/_/" in extras/rpm/Makefile, full 
line:

RELEASE=$(shell echo $(BASENAME) | cut -f3- -d- | sed -e s/-/_/g)

It seems really out of place, and leads to lots of difficulty in tracking down 
the place where something that looks like "foo-bar-blech" becomes 
"foo-bar_blech", for no obvious reason.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11642): https://lists.fd.io/g/vpp-dev/message/11642
Mute This Topic: https://lists.fd.io/mt/28789545/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to