From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tim.rpsys.net (93-97-173-237.zone5.bethere.co.uk [93.97.173.237]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id D79C7E01366 for ; Wed, 4 Jan 2012 06:33:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q04EX9gQ019718; Wed, 4 Jan 2012 14:33:09 GMT Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 19653-01; Wed, 4 Jan 2012 14:33:05 +0000 (GMT) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q04EX28G019712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Jan 2012 14:33:04 GMT Message-ID: <1325687580.20759.4.camel@ted> From: Richard Purdie To: Gary Thomas Date: Wed, 04 Jan 2012 14:33:00 +0000 In-Reply-To: <4F045A23.7070208@mlbassoc.com> References: <4F045A23.7070208@mlbassoc.com> X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Cc: poky@yoctoproject.org Subject: Re: Can't build vte X-BeenThere: poky@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Poky build system developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 14:33:18 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Wed, 2012-01-04 at 06:54 -0700, Gary Thomas wrote: > It seems that master is rather broken at the moment. > > OE Build Configuration: > BB_VERSION = "1.15.0" > TARGET_ARCH = "arm" > TARGET_OS = "linux-gnueabi" > MACHINE = "beagleboard" > DISTRO = "poky" > DISTRO_VERSION = "1.1+snapshot-20120104" > TUNE_FEATURES = "armv7a vfp neon cortexa8" > TARGET_FPU = "vfp-neon" > meta > meta-yocto = "master:f3a1a8897c78e116d7d28947a85687d0ce9d7df7" > > 'bitbake vte' fails to configure. Log attached. There is a fix in master for that: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=93855361b76565bef7b8cc5b474a51b20b328464 We're working through a backlog of changes from over the holidays but fixes are being worked on for known issues. Cheers, Richard