From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ferruh.yigit@intel.com>
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24])
 by dpdk.org (Postfix) with ESMTP id 4CD155584
 for <dev@dpdk.org>; Tue,  5 Jul 2016 13:27:12 +0200 (CEST)
Received: from orsmga001.jf.intel.com ([10.7.209.18])
 by orsmga102.jf.intel.com with ESMTP; 05 Jul 2016 04:27:11 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.26,579,1459839600"; d="scan'208";a="989400619"
Received: from nnguy21-mobl3.ccr.corp.intel.com (HELO [10.255.149.189])
 ([10.255.149.189])
 by orsmga001.jf.intel.com with ESMTP; 05 Jul 2016 04:27:08 -0700
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>, dev@dpdk.org
References: <1459865290-10248-1-git-send-email-adrien.mazarguil@6wind.com>
 <cover.1467715254.git.adrien.mazarguil@6wind.com>
Cc: Jan Viktorin <viktorin@rehivetech.com>
From: Ferruh Yigit <ferruh.yigit@intel.com>
Message-ID: <577B998A.4050009@intel.com>
Date: Tue, 5 Jul 2016 12:27:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <cover.1467715254.git.adrien.mazarguil@6wind.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-dev] [PATCH v2 00/11] Fix build errors related to
 exported headers
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2016 11:27:12 -0000

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 when enabling strict error/standard checks (-std and
> -pedantic for instance).

Out of curiosity, is there a specific standard version that is targeted?