From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/6] tcmode-default: Bump gcc,glibc,gdb
Date: Wed, 25 May 2016 14:56:18 +0100 [thread overview]
Message-ID: <1464184578.9570.100.camel@linuxfoundation.org> (raw)
In-Reply-To: <7091d7d0-b03c-2dfd-eee9-d160f3a944a2@windriver.com>
On Wed, 2016-05-25 at 09:31 -0400, Bruce Ashfield wrote:
> Hmm. Are we somehow building different SRCREVs ? I'm able to build
> the
> ppc kernel with gcc6:
>
> yow-bashfiel-d4 [/home/bruc...dard-build]> ls -alF vmlinux
> -rwxr-xr-x 1 bruce bruce 115353128 May 25 09:12 vmlinux*
> yow-bashfiel-d4 [/home/bruc...dard-build]> pwd
> /home/bruce/poky/build/tmp/work/qemuppc-poky-linux/linux
> -yocto/4.4.11+gitAUTOINC+6ec93aaa70_628bf62756-r0/linux-qemuppc
> -standard-build
> yow-bashfiel-d4 [/home/bruc...dard-build]> ls -alF vmlinux
> -rwxr-xr-x 1 bruce bruce 115353128 May 25 09:12 vmlinux*
> yow-bashfiel-d4 [/home/bruc...dard-build]> strings vmlinux | grep
> "gcc
> version"
> %s version %s (bruce@yow-bashfiel-d4) (gcc version 6.1.1 20160511
> (GCC) ) %s
> Linux version 4.4.11-yocto-standard (bruce@yow-bashfiel-d4) (gcc
> version
> 6.1.1 20160511 (GCC) ) #1 PREEMPT Wed May 25 09:12:02 EDT 2016
The autobuilder failure is here:
https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/8
07/steps/BuildImages_1/logs/stdio
which shows:
4.4.11+gitAUTOINC+6ec93aaa70_df00877ef9-r0
so yes, we're not seeing the same latter revision. The next obvious
question is why, have I missed a patch?
Cheers,
Richard
next prev parent reply other threads:[~2016-05-25 13:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 16:46 [PATCH 0/6] Glibc/gdb upgrade switch to gcc-6 as default Khem Raj
2016-05-13 16:46 ` [PATCH 1/6] glibc: Add recipes for 2.24 release Khem Raj
2016-07-03 13:45 ` Trevor Woerner
2016-07-03 15:02 ` Khem Raj
2016-07-05 14:56 ` Trevor Woerner
2016-05-13 16:46 ` [PATCH 2/6] python-native: Point to expat in native sysroot and add missing dep on expat-native Khem Raj
2016-05-13 16:46 ` [PATCH 3/6] gdb: Upgrade to 7.11 Khem Raj
2016-05-13 16:46 ` [PATCH 4/6] tcmode-default: Bump gcc,glibc,gdb Khem Raj
2016-05-15 7:03 ` Richard Purdie
2016-05-15 9:25 ` Khem Raj
2016-05-16 12:49 ` Bruce Ashfield
2016-05-16 13:38 ` Bruce Ashfield
2016-05-24 14:51 ` Richard Purdie
2016-05-24 15:51 ` Bruce Ashfield
2016-05-24 18:18 ` Khem Raj
2016-05-25 6:39 ` Richard Purdie
2016-05-25 8:23 ` Khem Raj
2016-05-25 12:03 ` Bruce Ashfield
2016-05-25 12:01 ` Bruce Ashfield
2016-05-25 12:32 ` Bruce Ashfield
2016-05-25 13:31 ` Bruce Ashfield
2016-05-25 13:56 ` Richard Purdie [this message]
2016-05-25 14:15 ` Richard Purdie
2016-05-25 14:16 ` Bruce Ashfield
2016-05-26 14:15 ` Richard Purdie
2016-05-26 14:17 ` Bruce Ashfield
2016-05-13 16:46 ` [PATCH 5/6] linux-yocto/4.4: gcc6 build fixes (powerpc and mips) Khem Raj
2016-05-13 16:46 ` [PATCH 6/6] feature-arm-vfp.inc: fix overzealous ARMPKGSFX_FPU modification Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1464184578.9570.100.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox