From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by mail.openembedded.org (Postfix) with ESMTP id 4A557601F7 for ; Mon, 27 Jul 2015 13:56:03 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.15.1/8.15.1) with ESMTPS id t6RDu1M5021487 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Jul 2015 06:56:02 -0700 (PDT) Received: from [128.224.56.48] (128.224.56.48) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.3.235.1; Mon, 27 Jul 2015 06:55:47 -0700 Message-ID: <55B6386B.7010408@windriver.com> Date: Mon, 27 Jul 2015 09:55:55 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Richard Purdie References: <1437989436.821.221.camel@linuxfoundation.org> <55B6300F.7060104@windriver.com> <1438005162.821.253.camel@linuxfoundation.org> In-Reply-To: <1438005162.821.253.camel@linuxfoundation.org> Cc: Otavio Salvador , openembedded-core Subject: Re: gcc 5.2 failures X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jul 2015 13:56:04 -0000 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit On 15-07-27 09:52 AM, Richard Purdie wrote: > On Mon, 2015-07-27 at 09:20 -0400, Bruce Ashfield wrote: >> On 15-07-27 05:30 AM, Richard Purdie wrote: >>> I've run a gcc 5.2 test build on the autobuilder: >>> >>> http://errors.yoctoproject.org/Errors/Search/?items=10&query=3628c3c06fa4195003ac655bcc791acfac775173&limit=50 >>> >>> 41 errors (with a few more pending). >>> >>> The good news is that if we tweak the security flags, the poky-lsb gcc, >>> elfutils, coreutils and iptables issues can be removed and I have a >>> patch for this. This leaves: >>> >>> 3.14 kernel failures for edgerouter, genericx86-64, qemuarm, beaglebone, >>> mpc8315e-rdb >> >> Gah. I had all these building with 5.1 .. chasing gcc is a pain >> with this older kernel. > > I'm not sure if this is a 5.1 verses 5.2 issue or not. I'm starting to > wonder if the SRCREVs we're using pull in the gcc 5.x fixes? Hmm. True enough, I'll double check, since I did have everything building against 5.1 about a week ago. > > E.g. one of the failures was: > > /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/build/build/tmp/work-shared/beaglebone/kernel-source/include/linux/compiler-gcc.h:106:30: fatal error: linux/compiler-gcc5.h: No such file or directory > > which doesn't look "5.2". > >>> Bruce: How do you want to handle the 3.14 issues? Switch to 4.1? or fix >>> 3.14? >> >> Now that 4.1 is in place, and I can't really see a large user base that >> needs gcc 5.x with the linux-yocto 3.14 kernel (other folks using >> master with their own kernel's will obviously have to deal with the >> issue in their trees) .. join that with the fact that we need to update >> all the reference boards to 4.1 anyway, my suggestion is that we open >> bugs for the h/w reference updates (and I'll get the appropriate Wind >> River eyes on them) and walk away from burning more cycles on gcc 5.x >> and the 3.14 kernel. > > That seems reasonable to me, assuming we don't have an easy SRCREV fix > we've just missed/lost somehow... I'll get back to you on that one, I'm turning 5.x back on in my local builds. Bruce > > Cheers, > > Richard >