From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Red Hat 6.5 compilation failure
Date: Mon, 31 Oct 2016 12:27:29 +0100 [thread overview]
Message-ID: <3394000.hODjKmm7Ki@xps13> (raw)
In-Reply-To: <20161031104318.GC4823@autoinstall.dev.6wind.com>
2016-10-31 11:43, Nélio Laranjeiro:
> Hi all,
>
> Am facing an issue with compilation on redhat 6.5 of DPDK v16.11-rc2,
Thanks Nelio for raising the issue.
> compilation fails with:
[...]
> In doc/guides/rel_notes/supported_os.rst we still support
> "Red Hat Enterprise Linux 6.5".
>
> Do we still want to support it, or should we update the documentation to
> remove it?
I vote for dropping RHEL6 support in DPDK 16.11.
Any other comment in the community?
Please give your voice, whether you agree or disagree.
next prev parent reply other threads:[~2016-10-31 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 10:43 Nélio Laranjeiro
2016-10-31 11:27 ` Thomas Monjalon [this message]
2016-10-31 14:16 ` Neil Horman
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=3394000.hODjKmm7Ki@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
/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).