From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Daniel Pharos <danielpharos@hotmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Compilation failure when disabling Cavium OCTEONTX network PMD driver
Date: Sun, 7 Jul 2019 13:00:39 +0000 [thread overview]
Message-ID: <BYAPR18MB242469307051C7887E05E018C8F70@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <AM0PR0402MB38268D9F7F77DB2B2E1FCA1ED3F40@AM0PR0402MB3826.eurprd04.prod.outlook.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Daniel Pharos
> Sent: Saturday, July 6, 2019 8:41 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Compilation failure when disabling Cavium OCTEONTX
> network PMD driver
>
> Hi,
>
> If I disable the Cavium OCTEONTX network PMD driver in the config file (so:
> "CONFIG_RTE_LIBRTE_OCTEONTX_PMD=n"), compilation of DPDK 19.05 fails
> with:
CONFIG_RTE_LIBRTE_PMD_OCTEONTX_SSOVF is depended on
CONFIG_RTE_LIBRTE_OCTEONTX_PMD.
Please disable CONFIG_RTE_LIBRTE_PMD_OCTEONTX_SSOVF as well.
next prev parent reply other threads:[~2019-07-07 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 15:11 Daniel Pharos
2019-07-07 13:00 ` Jerin Jacob Kollanukkaran [this message]
[not found] ` <AM0PR0402MB3826002A98D18716BA6359FAD3F70@AM0PR0402MB3826.eurprd04.prod.outlook.com>
[not found] ` <BYAPR18MB24247C55F57AF4FF16AFEA4AC8F70@BYAPR18MB2424.namprd18.prod.outlook.com>
[not found] ` <AM0PR0402MB3826109D818BFCB759E3B55CD3F70@AM0PR0402MB3826.eurprd04.prod.outlook.com>
[not found] ` <BYAPR18MB24243551F2EAADFBE6C151CFC8F70@BYAPR18MB2424.namprd18.prod.outlook.com>
[not found] ` <AM0PR0402MB3826565C7F5856751401D081D3F60@AM0PR0402MB3826.eurprd04.prod.outlook.com>
[not found] ` <BYAPR18MB24248589B21F5F628BD40B3BC8F60@BYAPR18MB2424.namprd18.prod.outlook.com>
[not found] ` <AM0PR0402MB3826CA93FB8CB565A8BE1435D3F60@AM0PR0402MB3826.eurprd04.prod.outlook.com>
2019-07-08 21:16 ` Daniel Pharos
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=BYAPR18MB242469307051C7887E05E018C8F70@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=danielpharos@hotmail.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).