From: Thomas F Herbert <therbert@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Shared library build broken
Date: Mon, 08 Jun 2015 16:14:10 -0400 [thread overview]
Message-ID: <5575F792.8080306@redhat.com> (raw)
I just noticed that shared library build is broking. I am building
current master. I had to make this change to get it to build:
-CONFIG_RTE_LIBRTE_PMD_BOND=y
+CONFIG_RTE_LIBRTE_PMD_BOND=n
One of the recent bonding commits broke some dependencies I think but I
didn't investigate further.
test_link_bonding.o: In function `test_add_slave_to_bonded_device':
test_link_bonding.c:(.text+0x44a): undefined reference to
`rte_eth_bond_slave_add'
test_link_bonding.c:(.text+0x462): undefined reference to
`rte_eth_bond_slaves_get'
test_link_bonding.c:(.text+0x487): undefined reference to
`rte_eth_bond_active_slaves_get
....
--TFH
next reply other threads:[~2015-06-08 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 20:14 Thomas F Herbert [this message]
2015-06-08 21:29 ` Thomas F Herbert
2015-06-09 9:40 ` Gonzalez Monroy, Sergio
2015-06-09 13:28 ` Thomas F Herbert
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=5575F792.8080306@redhat.com \
--to=therbert@redhat.com \
--cc=dev@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).