From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by dpdk.org (Postfix) with ESMTP id 3AB3E6849 for ; Tue, 31 Mar 2015 17:27:46 +0200 (CEST) Received: by obvd1 with SMTP id d1so31919559obv.0 for ; Tue, 31 Mar 2015 08:27:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=gQqgDcEvp+P+72WnvWDgBctWwGR+2YsFUkRpry7Ow+c=; b=BMQVXNVjs2Evs32+1PTdhLOXyofewwzSTbtFpfWXywCS9+BhelzM4FHCR5zYePa19/ z989gE/LPs227G+X87pSiZscD5akgRTzSIw/YD61zLF1iSM9YaIylJUHyFhyaEsIXycR l7t30lMxVHym8Azm4Rz4ld1BeMPejGOEEgr4wfDzglthcMhazQ43h53wIcZfm+2heKmN +E3GsLTIL1BhqzE1rMF1wGK580Xf+LKOOR6BH7c63wyzkzmXSwE5GIfQhWs7Clw3p9Ye 5quotfXeaflLnhP0jEPTkcs8m+ZmRPhNmShgIgjNa+J00erXwpJKKwwzdDzIL5wKaVm8 tnqw== X-Gm-Message-State: ALoCoQnWnnMUoTcfCttVECLfzmi2t067eyBZ1w6gsGqBc5e+f+VnjKax2e0+Uwf/QWYjNX3NQjsl X-Received: by 10.60.123.83 with SMTP id ly19mr33536621oeb.8.1427815660922; Tue, 31 Mar 2015 08:27:40 -0700 (PDT) Received: from localhost (199-87-125-144.dyn.kc.surewest.net. [199.87.125.144]) by mx.google.com with ESMTPSA id x8sm4727254oey.12.2015.03.31.08.27.40 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Tue, 31 Mar 2015 08:27:40 -0700 (PDT) Date: Tue, 31 Mar 2015 10:27:17 -0500 From: Seth Forshee To: "Ananyev, Konstantin" Message-ID: <20150331152717.GC99112@ubuntu-hedt> References: <20150331144108.GB99112@ubuntu-hedt> <2601191342CEEE43887BDE71AB9772582141330E@irsmsx105.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2601191342CEEE43887BDE71AB9772582141330E@irsmsx105.ger.corp.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Build failure in v2.0.0-rc3 with !CC_AVX2_SUPPORT X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 15:27:46 -0000 On Tue, Mar 31, 2015 at 02:59:36PM +0000, Ananyev, Konstantin wrote: > > > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Seth Forshee > > Sent: Tuesday, March 31, 2015 3:41 PM > > To: dev@dpdk.org > > Subject: [dpdk-dev] Build failure in v2.0.0-rc3 with !CC_AVX2_SUPPORT > > > > I'm getting errors when building DPDK in an Ubuntu 15.04 VM with > > T=x86_64-native-linuxapp-gcc. I've got a small VM set up without avx2 in > > the cpu flags: > > > > $ cat /proc/cpuinfo > > processor : 0 > > vendor_id : GenuineIntel > > cpu family : 6 > > model : 6 > > model name : QEMU Virtual CPU version 2.0.0 > > stepping : 3 > > microcode : 0x1 > > cpu MHz : 2993.068 > > cache size : 4096 KB > > physical id : 0 > > siblings : 1 > > core id : 0 > > cpu cores : 1 > > apicid : 0 > > initial apicid : 0 > > fpu : yes > > fpu_exception : yes > > cpuid level : 4 > > wp : yes > > flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm rep_good nopl > > pni vmx cx16 x2apic popcnt hypervisor lahf_lm abm vnmi ept > > > It seems that your VM cpu doesn't even have SSE3. > As I remember, DPDK doesn't support architectures prior to SSE3, i.e you need a VM with at least core2 CPU. This VM was set up with a script that just uses the qemu default CPU, which is quite basic. Bumping it up to a core2 with SSE3 but not avx does get the build working. So if that CPU lacks features required by DPDK then I guess there's no problem, I just didn't know how to interpret those build errors. Thanks, Seth