From: Bruce Richardson <bruce.richardson@intel.com>
To: Ben Magistro <koncept1@gmail.com>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>,
<david.marchand@redhat.com>, <mb@smartsharesystems.com>,
<roretzla@linux.microsoft.com>
Subject: Re: [RFC PATCH 0/1] Specify C-standard requirement for DPDK builds
Date: Fri, 3 Feb 2023 15:09:40 +0000 [thread overview]
Message-ID: <Y90jtNQbpXU2SsdA@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAKx8PBiGPxpJntFRHBieZHL5Sa0HKRGhSsOpJcheNeXR7hmZAQ@mail.gmail.com>
On Fri, Feb 03, 2023 at 09:09:14AM -0500, Ben Magistro wrote:
> Since this topic keeps coming up in other threads I'll chime in with my
> $0.01 here. We've been using CentOS 7 for awhile (and working on
> migrating off) but have had to leverage devtoolset/llvmtoolset for
> various reasons. I remember a discussion of installing a different
> compiler coming up but don't remember which thread that was in/what the
> outcome was. While I'd like to just brush over C7 and say there is a
> compatible compiler available so just make the change I also realize
> that making that change could be quite disruptive to existing code
> bases.
> However, the 22.11 LTS will be EOL in Nov 2024. CentOS 7 is EOL Jun
> 2024. For the 23.x series and going forward I don't think starting
> with a C11 requirement is an unreasonable ask.
>
Thanks for that input. If we drop support for Centos/RHEL 7, I think we
should be ok to pass -std=c11 for the build of DPDK.
Have you any thoughts on the second part of the c11 move - where our
headers require c11 support and therefore may require that the end user
builds their own code using -std=c11? This latter part is the bit that
concerns me a little, as I feel it may be problematic for some with older
codebases.
/Bruce
next prev parent reply other threads:[~2023-02-03 15:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 11:35 Bruce Richardson
2023-01-12 11:35 ` [RFC PATCH 1/1] build: increase minimum C standard " Bruce Richardson
2023-01-12 12:42 ` Morten Brørup
2023-01-12 12:47 ` Bruce Richardson
2023-01-12 15:06 ` Morten Brørup
2023-01-12 17:04 ` Tyler Retzlaff
2023-02-03 14:09 ` [RFC PATCH 0/1] Specify C-standard requirement " Ben Magistro
2023-02-03 15:09 ` Bruce Richardson [this message]
2023-02-03 16:45 ` Ben Magistro
2023-02-03 18:00 ` Bruce Richardson
2023-02-10 14:52 ` Ben Magistro
2023-02-10 23:39 ` Tyler Retzlaff
2023-02-22 18:53 ` Tyler Retzlaff
2023-02-23 9:44 ` Bruce Richardson
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=Y90jtNQbpXU2SsdA@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=koncept1@gmail.com \
--cc=mb@smartsharesystems.com \
--cc=roretzla@linux.microsoft.com \
--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).