2016-07-05 12:44, Adrien Mazarguil:
> This patchset affects exported headers only, compilation problems are
> addressed as follows:
I prefer postponing the headers changes to the very first days of
the 16.11 cycle.
On Tue, Jul 05, 2016 at 12:27:06PM +0100, Ferruh Yigit wrote:
> On 7/5/2016 11:44 AM, Adrien Mazarguil wrote:
> > DPDK uses GNU C language extensions in most of its code base. This is fine
> > for internal source files whose compilation flags are controlled by DPDK,
> > however user applications th
2016-07-05 12:27, Ferruh Yigit:
> On 7/5/2016 11:44 AM, Adrien Mazarguil wrote:
> > DPDK uses GNU C language extensions in most of its code base. This is fine
> > for internal source files whose compilation flags are controlled by DPDK,
> > however user applications that use exported "public" heade
Hi Jan,
On Tue, Jul 05, 2016 at 01:15:23PM +0200, Jan Viktorin wrote:
> Hi Adrien,
>
> I am the only one in CC and only in the 00/11 patch. Is it a mistake? Or what
> is the purpose?
It was on purpose to draw your attention to my comment regarding #includes
within extern "C" blocks.
> Regards?
Hi Adrien,
I am the only one in CC and only in the 00/11 patch. Is it a mistake? Or what
is the purpose?
Regards?
Jan?Viktorin
RehiveTech
Sent?from?a?mobile?device
? P?vodn? zpr?va ?
Od: Adrien Mazarguil
Odesl?no: ?ter?, 5. ?ervence 2016 12:45
Komu: dev at dpdk.org
Kopie: Jan Viktorin
P?edm?t: [
DPDK uses GNU C language extensions in most of its code base. This is fine
for internal source files whose compilation flags are controlled by DPDK,
however user applications that use exported "public" headers may experience
compilation failures when enabling strict error/standard checks (-std and
On 7/5/2016 11:44 AM, Adrien Mazarguil wrote:
> DPDK uses GNU C language extensions in most of its code base. This is fine
> for internal source files whose compilation flags are controlled by DPDK,
> however user applications that use exported "public" headers may experience
> compilation failures
7 matches
Mail list logo
