From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id AB363E00BEA; Wed, 18 Jun 2014 15:14:38 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=HTML_MESSAGE,KHOP_DYNAMIC autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.0 KHOP_DYNAMIC Relay looks like a dynamic address Received: from www.dynamicdevices.co.uk (www.dynamicdevices.co.uk [89.200.136.37]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 43A99E00AFD for ; Wed, 18 Jun 2014 15:14:26 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by www.dynamicdevices.co.uk (Postfix) with ESMTP id 2124A27E037; Wed, 18 Jun 2014 22:14:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at lennoab2.miniserver.com Received: from www.dynamicdevices.co.uk ([127.0.0.1]) by localhost (www.dynamicdevices.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gP2DhanMn-y0; Wed, 18 Jun 2014 22:14:21 +0000 (UTC) Received: from [127.0.0.1] (cpc32-live22-2-0-cust59.17-2.cable.virginm.net [82.36.253.60]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by www.dynamicdevices.co.uk (Postfix) with ESMTPSA id 7A81927E031; Wed, 18 Jun 2014 22:14:21 +0000 (UTC) Message-ID: <53A20F35.9060700@dynamicdevices.co.uk> Date: Wed, 18 Jun 2014 23:14:13 +0100 From: Alex J Lennon User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Ruud den Bekker , yocto@yoctoproject.org References: <21598C768CAB7B46B75C18783A59ACEE271D1A@cordissvr01.Cordis.local> In-Reply-To: <21598C768CAB7B46B75C18783A59ACEE271D1A@cordissvr01.Cordis.local> X-Enigmail-Version: 1.6 Subject: Re: build error X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2014 22:14:38 -0000 Content-Type: multipart/alternative; boundary="------------040907060907020703040508" --------------040907060907020703040508 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 18/06/2014 09:38, Ruud den Bekker wrote: > > L.S., > > > > I followed the directions on > http://www.codeproject.com/Articles/774826/Adding-rd-party-components-to-Yocto-OpenEmbedded-L > > to add an example project to my yocto-poky build tree. > > > > a strange thing happens: > > when using bitbake bbexample-lt for "qemuarm" or "edgerouter", it > builds ok. > > however,if I select "beaglebone" for "MACHINE", I get a configure > error in my log file: > > > > "configure:3024: checking for C compiler version > > configure:3033: arm-poky-linux-gnueabi-gcc -march=armv7-a > -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 > --sysroot=/home/ruud/poky-daisy-11.0.0/build/tmp/sysroots/beaglebone > --version >&5 > > /home/ruud/poky-daisy-11.0.0/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/bbexample-lt/1.0-r0/bbexample-1.0/configure: > line 3035: arm-poky-linux-gnueabi-gcc: command not found" > > > > However, the building e.g. a "core-image-minimal" or my added > "core-image-mono" for a "beaglebone" builds fine and I can use the RFS > on a "real" hardware board. > > > Hi Ruud, I checked this through for the Beaglebone and it builds OK. - git cloned meta-ti - setup a new build tree - MACHINE ??= 'beaglebone' in local.conf - Added meta-example layer to bblayers.conf $ bitbake bbexample ... BB_VERSION = "1.23.1" BUILD_SYS = "i686-linux" NATIVELSBSTRING = "Ubuntu-12.04" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "beaglebone" DISTRO = "poky" DISTRO_VERSION = "1.6+snapshot-20140618" TUNE_FEATURES = "arm armv7a vfp neon" TARGET_FPU = "vfp-neon" meta meta-yocto = "master:b5a928af721026795be7b7f68b2dd577408afbe5" meta-oe = "master:8316933b400ae6fda688637fcc3e202b38a8e12b" meta-ti = "master:f351978d956e199032db5302696587969f5c428e" meta-example = "master:5ee4f20b041bc886b1d2d913ac11814057317634" Given you're having other issues too, it might be worth you trying a simple build in a clean tree? Regards, Alex > What can be the cause of this? > > > > Best regards, > > > > Ruud > > > > Ruud den Bekker > > Cordis Automation B.V. > > High Tech Campus 9 > > 5656 AE Eindhoven > > > > > --------------040907060907020703040508 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 18/06/2014 09:38, Ruud den Bekker wrote:

L.S.,

 

I followed the directions on http://www.codeproject.com/Articles/774826/Adding-rd-party-components-to-Yocto-OpenEmbedded-L

to add an example project to my yocto-poky build tree.

 

a strange thing happens:

when using bitbake bbexample-lt  for “qemuarm” or “edgerouter”, it builds ok.

however,if I select “beaglebone” for “MACHINE”, I get a configure error in my log file:

 

“configure:3024: checking for C compiler version

configure:3033: arm-poky-linux-gnueabi-gcc  -march=armv7-a -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 --sysroot=/home/ruud/poky-daisy-11.0.0/build/tmp/sysroots/beaglebone --version >&5

/home/ruud/poky-daisy-11.0.0/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/bbexample-lt/1.0-r0/bbexample-1.0/configure: line 3035: arm-poky-linux-gnueabi-gcc: command not found”

 

However, the building e.g. a “core-image-minimal” or my added “core-image-mono” for a “beaglebone” builds fine and I can use the RFS on a “real” hardware board.

 


Hi Ruud,

I checked this through for the Beaglebone and it builds OK.

- git cloned meta-ti
- setup a new build tree
- MACHINE ??= 'beaglebone' in local.conf
- Added meta-example layer to bblayers.conf

$ bitbake bbexample

...

BB_VERSION        = "1.23.1"
BUILD_SYS         = "i686-linux"
NATIVELSBSTRING   = "Ubuntu-12.04"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "beaglebone"
DISTRO            = "poky"
DISTRO_VERSION    = "1.6+snapshot-20140618"
TUNE_FEATURES     = "arm armv7a vfp neon"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto        = "master:b5a928af721026795be7b7f68b2dd577408afbe5"
meta-oe           = "master:8316933b400ae6fda688637fcc3e202b38a8e12b"
meta-ti           = "master:f351978d956e199032db5302696587969f5c428e"
meta-example      = "master:5ee4f20b041bc886b1d2d913ac11814057317634"

Given you're having other issues too, it might be worth you trying a simple build in a clean tree?

Regards,

Alex

What can be the cause of this?

 

Best regards,

 

Ruud

 

Ruud den Bekker

Cordis Automation B.V.

High Tech Campus 9

5656 AE Eindhoven

 




--------------040907060907020703040508--