That patch in question is now merged to branch v21.01.x.
The builds performed for latest SPDK and SPDK LTS, against dpdk-main branch seem to be
passing. Would love to hear if this is what you are seeing on your end too.
From: Lincoln Lavoie <lylavoie(a)iol.unh.edu>
Sent: Monday, February 8, 2021 5:21 PM
To: Zawadzki, Tomasz <tomasz.zawadzki(a)intel.com>
Cc: Aaron Conole <aconole(a)redhat.com>; Brandon Lo <blo(a)iol.unh.edu>;
dpdklab(a)iol.unh.edu; ci(a)dpdk.org; dev(a)dpdk.org; spdk(a)lists.01.org
Subject: Re: [dpdk-ci] [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab
Can you let us know when the merge happens and we'll make sure the next set of builds
pass or see what the next failure is. :-P
On Mon, Feb 8, 2021 at 11:03 AM Zawadzki, Tomasz
Thank you for reporting this !
This is an issue with rte_power now depending on rte_ethdev, which was resolved on latest
I believe that UNH lab verifies DPDK patches against SPDK branch for latest release. Which
after the very recent SPDK release, would be v21.01.x:
The fix has been backported to that branch and should be merged shortly:
From: dev <email@example.com<mailto:firstname.lastname@example.org>> On Behalf Of
Sent: Monday, February 8, 2021 4:21 PM
To: Brandon Lo <email@example.com<mailto:firstname.lastname@example.org>>
Subject: [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab
I've noticed that recently SPDK compilation in the UNH community lab seems
to be failing, and I don't see an obvious reason for the failure.
The logs haven't been too helpful - it appears that there is a symbol that
available when linking.
Job details (for example):
Is it possible to turn on more verbose logging during the compilation of
SPDK? Maybe show the arguments to the compiler for the specific object?
Maybe the SPDK folks can see something obviously wrong?
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
[Image removed by sender.]<https://www.iol.unh.edu/>