From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 45FFC1B561 for ; Tue, 9 Oct 2018 15:54:53 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Oct 2018 06:54:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,360,1534834800"; d="scan'208";a="97436106" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga001.fm.intel.com with ESMTP; 09 Oct 2018 06:54:09 -0700 Received: from fmsmsx124.amr.corp.intel.com (10.18.125.39) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 9 Oct 2018 06:54:09 -0700 Received: from fmsmsx117.amr.corp.intel.com ([169.254.3.34]) by fmsmsx124.amr.corp.intel.com ([169.254.8.48]) with mapi id 14.03.0319.002; Tue, 9 Oct 2018 06:54:09 -0700 From: "Wiles, Keith" To: Cliff Burdick CC: users Thread-Topic: [dpdk-users] RTE_MACHINE_TYPE Error Thread-Index: AQHUX4YfriA+yTl6nkG5WBM+rfz1HqUXZWUA Date: Tue, 9 Oct 2018 13:54:08 +0000 Message-ID: <2099488D-C9CD-4989-AF1F-18EA9F558717@intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.255.69.176] Content-Type: text/plain; charset="us-ascii" Content-ID: <07C03CCF6A091E44AB6C6F93BE87F8F2@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] RTE_MACHINE_TYPE Error X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2018 13:54:53 -0000 > On Oct 8, 2018, at 11:10 PM, Cliff Burdick wrote: >=20 > Hi, I'm trying to compile on a machine with an older-generation xeon than > the target, so I'm using CONFIG_RTE_MACHINE=3D"broadwell" in the config. > gcc's options show that broadwell supports the AES flag, and I verified > that the build shows -march=3Dbroadwell. However, when I run my applicati= on > it prints immediately: >=20 > ERROR: This system does not support "AES". > Please check that RTE_MACHINE is set correctly. > EAL: FATAL: unsupported cpu type. > EAL: unsupported cpu type. > EAL: Error - exiting with code: 1 > Cause: Error with EAL initialization >=20 > This is gcc 7, so it supports that flag. Does anyone know how I can compi= le > for a later architecture on an older machine? Have you checked to make sure the CPU does support the feature by looking t= hat the CPU flags in /proc/cpuinfo ? Normally this is the reason the code will not run is the CPU does not suppo= rt it. Regards, Keith