From: Shahar Salzman <shahar.salzman@kaminario.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Compiling DPDK with CentOS6
Date: Mon, 7 May 2018 07:15:16 +0000 [thread overview]
Message-ID: <AM3PR04MB370576A3A0C094044917DD5899B0@AM3PR04MB370.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1726788.9oXxB9efqE@xps>
OK, we are building dpdk from sources, used version 16.07, but would like to upgrade to a newer version in order to be inline with spdk master.
On the supported OS page RHEL6.5 is mentioned as supported (uses the 4.4.X gcc collection), is the page outdated?
________________________________
From: Thomas Monjalon <thomas@monjalon.net>
Sent: Thursday, May 3, 2018 6:56:11 PM
To: Shahar Salzman
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Compiling DPDK with CentOS6
Hi
03/05/2018 16:20, Shahar Salzman:
> I am using spdk, hence dpdk. Following the termination of CentOS6
> support, I did some work in order to get dpdk to work on CentOS6
> (gcc version 4.4.7).
CentOS6 is really old.
> I had to remove some of the modules due to compilation errors,
> use -fno-strict-aliasing to avoid non issues dereferencing
> void* arrays and a single patch in the code which has to do
> with the way my gcc handles the attribure deprecated.
>
> I did all my work on dpdk tag v18.02.
> Would you consider taking some of this to dpdk?
> It would be really helpful for us to maintain support for
> CentOS6 and its toolchain, at least in the near future,
> and we would like to use the latest dpdk stable.
For such an old distribution, we cannot put expectations
on the latest releases of DPDK, unfortunately.
Is there a DPDK package for CentOS6?
If not, better to use old DPDK, or switch to a recent distribution.
next prev parent reply other threads:[~2018-05-07 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 14:20 Shahar Salzman
2018-05-03 15:56 ` Thomas Monjalon
2018-05-07 7:15 ` Shahar Salzman [this message]
2018-05-07 13:43 ` Thomas Monjalon
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=AM3PR04MB370576A3A0C094044917DD5899B0@AM3PR04MB370.eurprd04.prod.outlook.com \
--to=shahar.salzman@kaminario.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).