From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: Build is broken in dpdk-next-net Date: Tue, 03 Apr 2018 12:13:11 +0200 Message-ID: <30459437.oZxcDd1rdk@xps> References: <20180402092515.3e5ccea4@xeon-e3> <02f1e234-e02c-332c-bf09-77584621cef1@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Stephen Hemminger , Neil Horman , =?ISO-8859-1?Q?Ga=EBtan?= Rivet , Tonghao Zhang , Timothy Redaelli , Andrew Rybchenko , "dev@dpdk.org" , Ferruh Yigit To: Maxime Coquelin Return-path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 5FB061B68E for ; Tue, 3 Apr 2018 12:16:53 +0200 (CEST) In-Reply-To: <02f1e234-e02c-332c-bf09-77584621cef1@redhat.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 03/04/2018 10:31, Maxime Coquelin: > On 04/02/2018 06:25 PM, Stephen Hemminger wrote: > > Rather than wallpapering over the unused result, why not do real error checking? > > If the program was run in a non-Linux environment (such as WSL etc), maybe an error > > could occur. Best to return an error; or at least call rte_exit(). > > > > Do we really want to call rte_exit() in a library? No, we must use return.