From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (dan.rpsys.net [93.97.175.187]) by mx1.pokylinux.org (Postfix) with ESMTP id 6C8284C800A7 for ; Wed, 2 Feb 2011 12:00:57 -0600 (CST) Received: from localhost (dan.rpsys.net [127.0.0.1]) by dan.rpsys.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id p12I2wTV020069; Wed, 2 Feb 2011 18:02:58 GMT X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LYjJdd6eTIrC; Wed, 2 Feb 2011 18:02:58 +0000 (GMT) Received: from [192.168.1.42] (tim [93.97.173.237]) (authenticated bits=0) by dan.rpsys.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id p12I2nSP020064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 18:02:52 GMT From: Richard Purdie To: Darren Hart In-Reply-To: <4D49976E.5030800@linux.intel.com> References: <4D499346.4050800@mlbassoc.com> <4D49976E.5030800@linux.intel.com> Date: Wed, 02 Feb 2011 18:00:36 +0000 Message-ID: <1296669636.1544.4238.camel@rex> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Cc: Poky Subject: Re: Poky & armv5te 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, 02 Feb 2011 18:00:57 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Wed, 2011-02-02 at 09:42 -0800, Darren Hart wrote: > On 02/02/2011 09:24 AM, Gary Thomas wrote: > > I'd like to use Poky with my OMAP-L138 which is armv5te > > Sadly today, this just isn't a go because of GCC issues. > > I've tried all the combinations which are in the trees > > (main & contrib) with no luck: > > * 4.3.3 - fails to build GCC > > * 4.5.1 - everything builds but kernel crashes > > * 4.5.2 - fails to build GCC > > > > Am I totally out of luck? > > What are you running into? I've recently backported some changes in > support of the Beagleboard (armv7-a) which were necessary to build with > 4.5.1 and our 2.21 binutils. Those wouldn't affect armv5. What puzzles me is that qemuarm is effectively an armv5 like system and those do build and boot in qemu. When you managed images above for 4.5.1 did you try using a known good kernel with our userspace? I'm wondering if we can narrow it to a kernel issue? Cheers, Richard