From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-bk0-f47.google.com ([209.85.214.47]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SoVQA-0005I5-VB for openembedded-core@lists.openembedded.org; Tue, 10 Jul 2012 10:03:47 +0200 Received: by bkcik5 with SMTP id ik5so6343677bkc.6 for ; Tue, 10 Jul 2012 00:52:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=+kLo8dAzFZjhOzwoTB/rnnWnpY2SbqA4xWAuKR5NL08=; b=vSK99jWXE5K/Tw7i/RxLkUaOWnjiC8zwln1khOBK5tf9dP18YumbcJ6pNhG2KyKQ7I WKXEhD8++38DLB2aTR4Q98F3uegVTJLbDON6vCn/fPaFSnho/KKfw0dYZgFkMjvHaH/X OUOlkb4gvKU2sJWYcFn57oS5JP9OO1mg0mADjG5GMayXfHH9boE3pe0v8lAJ0yABSwkY wknc5hmUnqylEesCOEGHgQ3zstqcF4F2u8Y+tPs7fcGl1Ak2AKNBE38D/D2hq7EmoR1w zXIwY7xEGDLoUhnUQFtN6scadieL5NfC8ZGCLOVJiIYr1U4FSv6sZCdSi9QQCbCFHXF4 yAvA== Received: by 10.205.136.3 with SMTP id ii3mr21303610bkc.101.1341906756582; Tue, 10 Jul 2012 00:52:36 -0700 (PDT) Received: from localhost ([94.230.152.246]) by mx.google.com with ESMTPS id c18sm7554504bkv.8.2012.07.10.00.52.34 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 10 Jul 2012 00:52:35 -0700 (PDT) Date: Tue, 10 Jul 2012 09:52:33 +0200 From: Martin Jansa To: Patches and discussions about the oe-core layer Message-ID: <20120710075233.GK6308@jama.jama.net> References: <20120622063756.GK9352@jama.jama.net> <20120622073838.GL9352@jama.jama.net> MIME-Version: 1.0 In-Reply-To: <20120622073838.GL9352@jama.jama.net> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [PATCH 2/5] gcc-4.7: Update to tip of gcc-4_7-branch since 4.7.1 has been out X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2012 08:03:47 -0000 X-Groupsio-MsgNum: 25044 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DozTQjXnjm3C9Xhk" Content-Disposition: inline --DozTQjXnjm3C9Xhk Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 22, 2012 at 09:38:38AM +0200, Martin Jansa wrote: > On Fri, Jun 22, 2012 at 12:20:31AM -0700, Khem Raj wrote: > > On Thu, Jun 21, 2012 at 11:37 PM, Martin Jansa = wrote: > > > On Wed, Jun 20, 2012 at 08:18:37AM -0700, Khem Raj wrote: > > >> Signed-off-by: Khem Raj > > >> --- > > >> =A0meta/recipes-devtools/gcc/gcc-4.7.inc | =A0 12 ++++++------ > > >> =A01 files changed, 6 insertions(+), 6 deletions(-) > > >> > > >> diff --git a/meta/recipes-devtools/gcc/gcc-4.7.inc b/meta/recipes-de= vtools/gcc/gcc-4.7.inc > > >> index 34a73b1..25a1088 100644 > > >> --- a/meta/recipes-devtools/gcc/gcc-4.7.inc > > >> +++ b/meta/recipes-devtools/gcc/gcc-4.7.inc > > >> @@ -3,12 +3,12 @@ require gcc-common.inc > > >> =A0PR =3D "r2" > > >> > > >> =A0# Third digit in PV should be incremented after a minor release > > >> -# happens from this branch on gcc e.g. currently its 4.7.0 > > >> -# when 4.7.1 is releases and we bump SRCREV beyond the release > > >> -# on branch then PV should be incremented to 4.7.1+svnr${SRCPV} > > >> +# happens from this branch on gcc e.g. currently its 4.7.1 > > >> +# when 4.7.2 is releases and we bump SRCREV beyond the release > > >> +# on branch then PV should be incremented to 4.7.2+svnr${SRCPV} > > >> =A0# to reflect that change > > >> > > >> -PV =3D "4.7.0+svnr${SRCPV}" > > >> +PV =3D "4.7.1+svnr${SRCPV}" > > >> > > >> =A0# BINV should be incremented after updating to a revision > > >> =A0# after a minor gcc release (e.g. 4.7.1 or 4.7.2) has been made > > >> @@ -16,9 +16,9 @@ PV =3D "4.7.0+svnr${SRCPV}" > > >> =A0# 4.7.1 then the value below will have 2 which will mean 4.7.2 > > >> =A0# which will be next minor release and so on. > > >> > > >> -BINV =3D "4.7.1" > > >> +BINV =3D "4.7.2" > > >> > > >> -SRCREV =3D "186651" > > >> +SRCREV =3D "188658" > > >> =A0BRANCH =3D "gcc-4_7-branch" > > >> =A0FILESPATH =3D "${@base_set_filespath([ '${FILE_DIRNAME}/gcc-4.7' = ], d)}" > > > > > > I'm not sure if this one is new, but libgcc now reports unpackaged > > > file: > > > > > > NOTE: package libgcc-4.7.1+svnr188658-r2: task do_package: Started > > > WARNING: For recipe libgcc, the following files/directories were > > > installed but not shipped in any package: > > > WARNING: =A0 /usr/lib/arm-oe-linux-gnueabi/4.7.2/include > > > WARNING: =A0 /usr/lib/arm-oe-linux-gnueabi/4.7.2/include/unwind.h > >=20 > > can you see couple of things 1. if this file is being generated and > > installed during libgcc build or if its coming from the bits that are > > stashed away from gcc-cross build > >=20 > > this file should not be packaged with libgcc so right solution will be > > to delete this file > > > > > > And the problem with (sometimes) missing or corrupt header file is st= ill there: > > > | /OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7= -branch/gcc/dwarf2out.c:8383:6: warning: format not a string literal and no= format arguments [-Wformat-security] > > > | gcc -c =A0 -isystem/OE/shr-core/tmp-eglibc/sysroots/x86_64-linux/us= r/include -O2 -pipe -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE =A0-W -Wall -Wwrit= e-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-fo= rmat-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlengt= h-strings -Wold-style-definition -Wc++-compat =A0 -DHAVE_CONFIG_H -I. -I. -= I/OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch= /gcc -I/OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-= branch/gcc/. -I/OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/= gcc-4_7-branch/gcc/../include -I/OE/shr-core/tmp-eglibc/work-shared/gcc-4.7= =2E1+svnr188658-r2/gcc-4_7-branch/gcc/../libcpp/include =A0-I/OE/shr-core/t= mp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/gcc/../libdecn= umber -I/OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7= -branch/gcc/../libdecnumber/dpd -I../libdecnumber =A0 =A0/OE/shr-core/tmp-e= glibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/gcc/emit-rtl.c -o = emit-rtl.o > > > | /OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7= -branch/gcc/emit-rtl.c:42:17: fatal error: rtl.h: No such file or directory > > > | compilation terminated. > > > Restarting build helps again.. > > > > >=20 > > this is intriguing we should look into it can you explain (once again > > how can I reproduce it) >=20 > I still don't have any steps how to reproduce it reliably, just doing a > lot of gcc builds and I see about once from 5 builds.. So with every gcc > upgrade (even with just PR bump) I get usually at least 1 build failure > for 1 architecture/machine on one buildhost (sometimes it's on fast one, > sometimes on slow one with just 2 threads - so speed is not so important > to reproduce it). >=20 > Usually it's from gcc-cross-initial, but sometimes from intermediate or > gcc-cross itself too. >=20 > The error is different from time to time, but always some constant > missing or whole header file like in today's error. Probably most > popular one is > /OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.0+svnr186651-r1/gcc-4_7-branc= h/gcc/calls.c:1204:9: > error: 'STACK_CHECK_MAX_VAR_SIZE' undeclared (first use in this > function) >=20 > whole log in=20 > http://build.shr-project.org/tests/jama/gcc-issue/gcc-race-new/ >=20 > even more samples: > http://build.shr-project.org/tests/jama/gcc-upgrade-issue/ >=20 > I'm sorry I cannot provide better info. I guess this was caused by subversion-native in sstate checksums which was fixed in: http://git.openembedded.org/openembedded-core/commit/?id=3D793ce6cd9aa632e0= f13789c8293770a86085d28d because I was using subversion-native for long, so that can explain why I was only one seeing those gcc issues Cheers, --=20 Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com --DozTQjXnjm3C9Xhk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAk/730EACgkQN1Ujt2V2gBx+5wCfVZwD0nAVkya3Bu2Wsq3gaDJP giQAnRdj9ZY03C2w/vnKbKfKsxe5qbEE =H3n9 -----END PGP SIGNATURE----- --DozTQjXnjm3C9Xhk--