DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Patrick Robb <probb@iol.unh.edu>,
	Aaron Conole <aconole@redhat.com>,
	 dpdk-techboard <techboard@dpdk.org>
Cc: ci@dpdk.org, dev <dev@dpdk.org>
Subject: Disable SPDK testing again?
Date: Fri, 31 Oct 2025 09:38:32 +0100	[thread overview]
Message-ID: <CAJFAV8yS3-_RMn-Ln7umJFt+wWVH7Fj7yFnmmjgUnpD1=VX9yA@mail.gmail.com> (raw)

Hello,

The SPDK target in UNH lab has been spewing warnings as SPDK build
itself compiles and links against a list of libraries and drivers,
regardless of the upstream dependencies.
https://github.com/spdk/dpdk/commit/74b1a804eda2ed99d1ecaae5b79de7df6d74e8ff and
https://github.com/spdk/spdk/blob/master/dpdkbuild/Makefile#L66


Until SPDK fixes this on their side (either adding argparse in their
static list, or using pkg-config for example and stopping patching
DPDK), linking SPDK binaries fails as the argparse lib now necessary
to EAL is not pulled:

/usr/bin/ld.bfd:
/usr/local/lib/x86_64-linux-gnu/librte_eal.a(eal_common_eal_common_options.c.o):
in function `eal_usage':
eal_common_options.c:(.text+0x16): undefined reference to
`rte_argparse_print_help'
/usr/bin/ld.bfd:
/usr/local/lib/x86_64-linux-gnu/librte_eal.a(eal_common_eal_common_options.c.o):
in function `eal_collate_args':
eal_common_options.c:(.text+0x953): undefined reference to `rte_argparse_parse'
/usr/bin/ld.bfd:
/usr/local/lib/x86_64-linux-gnu/librte_eal.a(eal_common_eal_common_options.c.o):
in function `eal_parse_args':
eal_common_options.c:(.text+0x343b): undefined reference to
`rte_argparse_parse_type'
collect2: error: ld returned 1 exit status
make[3]: *** [/root/workspace/Generic-DPDK-Compile-Meson/spdk/mk/spdk.app.mk:39:
spdk_lock] Error 1
make[2]: *** [/root/workspace/Generic-DPDK-Compile-Meson/spdk/mk/spdk.subdirs.mk:16:
lock] Error 2
make[1]: *** [/root/workspace/Generic-DPDK-Compile-Meson/spdk/mk/spdk.subdirs.mk:16:
thread] Error 2


While it is just a warning in the CI dashboard, I don't think we
should waste resources on this testing.
Opinions?


-- 
David Marchand


             reply	other threads:[~2025-10-31  8:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31  8:38 David Marchand [this message]
2025-10-31  9:11 ` Morten Brørup
2025-10-31  9:17   ` David Marchand
2025-10-31 10:02     ` Morten Brørup
2025-10-31 15:13       ` Patrick Robb
2025-11-01  7:47         ` Morten Brørup

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJFAV8yS3-_RMn-Ln7umJFt+wWVH7Fj7yFnmmjgUnpD1=VX9yA@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=probb@iol.unh.edu \
    --cc=techboard@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).