From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id B09382F4F for ; Mon, 7 May 2018 15:43:40 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id C5C3321C6B; Mon, 7 May 2018 09:43:39 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 07 May 2018 09:43:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=z5vFT9zTfJ1ldbdJeG7JoVFDxh KPC0Ce8hMVix53TKc=; b=E2uChhUN9hI0g9EqmkBhtXnWAFhEi/Uk7m8qFMxO84 aO7w7TOlV8QxIP7ofXMow57CJ2MW5efDkymw8KBMvqDd2clijdkmhqHYSqWuzOiV krg3qQdNLxW2DMo+BKWSAAD10fUuhZhF0rGm1pUwy7lpj4ZZsJOQlJ495NUbTP7v E= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=z5vFT9 zTfJ1ldbdJeG7JoVFDxhKPC0Ce8hMVix53TKc=; b=d13cqBHQo11XXAJKdGZJXs UHTeF139m0oUC9AG52KcpFtrGTCrpDhuQ1x+pfyrKNCY6jEpHtxJUKnyG9O8k9KR Ex3bJbYyAG6kuMb5lqn1Q4+awJiL+Y9nTS/cwNYVt8n8sVOQMnfJ6ZgvXTCpZgJl RFdhxS67TEFbAXztY+msDR7wu3N9Y44lAURf1mHYxNmEtTcrMe9kHUwMUqvd0dZu W2trzxlxZClKwgzVk6dTBx2+cyeUq3SzSLIqXWLwuvc50L4yew2mgGORGXtBYFQi T6yUbjuIrHQWnc8G5MDxarZ2pJj+TAqs1BEOqftiJR6KRQkwR5UFgLmXWkNDKzlA == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 1AEF8E509E; Mon, 7 May 2018 09:43:39 -0400 (EDT) From: Thomas Monjalon To: Shahar Salzman Cc: "dev@dpdk.org" Date: Mon, 07 May 2018 15:43:37 +0200 Message-ID: <2682751.JPnioz8cGl@xps> In-Reply-To: References: <1726788.9oXxB9efqE@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Compiling DPDK with CentOS6 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2018 13:43:40 -0000 07/05/2018 09:15, Shahar Salzman: > 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? Yes, this page is outdated. I removed this page last year: http://dpdk.org/commit/fc2ffae923d2b > ________________________________ > From: Thomas Monjalon > 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.