From: john miller <john.miller@atomicrules.com>
To: dev@dpdk.org
Subject: [dpdk-dev] CentOS support for 17.11
Date: Mon, 16 Oct 2017 15:02:25 -0400 [thread overview]
Message-ID: <303A8729-D3AB-4FB6-971D-705376045428@atomicrules.com> (raw)
Hello,
We have been testing the dpdk-17.11-rc1 candidate on our Ubuntu platforms. We just tried to compile it on one of our CentOS platform and get this error.
== Build lib/librte_eal/linuxapp/igb_uio
CC [M] /projects/dpdk/dpdk-17.11-rc1/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
/projects/dpdk/dpdk-17.11-rc1/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c: In function ‘igbuio_pci_irqhandler’:
/projects/dpdk/dpdk-17.11-rc1/build/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:213:30: error: dereferencing pointer to incomplete type
struct uio_info *info = idev->info;
Description: CentOS Linux release 7.2.1511 (Core)
Is CentOS 7.2 still supported ?
Has anyone else run into this issue ?
I was not able to find the supported platforms doc for 17.11 online.
Thank you,
-John
next reply other threads:[~2017-10-16 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 19:02 john miller [this message]
2017-10-16 20:25 ` Ferruh Yigit
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=303A8729-D3AB-4FB6-971D-705376045428@atomicrules.com \
--to=john.miller@atomicrules.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).