From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>,
Saul Wold <sgw@linux.intel.com>,
<richard.purdie@linuxfoundation.org>,
"nitin.a.kamble" <nitin.a.kamble@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] linux-yocto/3.10: integrate LTSI
Date: Fri, 7 Feb 2014 11:57:36 -0500 [thread overview]
Message-ID: <52F51080.1000808@windriver.com> (raw)
In-Reply-To: <CF1A4F8F.6A6F9%dvhart@linux.intel.com>
On 14-02-07 11:55 AM, Darren Hart wrote:
> On 2/7/14, 8:48, "Bruce Ashfield" <bruce.ashfield@windriver.com> wrote:
>>>>>>> | ERROR: Function failed: do_compile (log file is located at
>>>>>>>
>>>>>>>
>>>>>>> /home/pokybuild/yocto-autobuilder-dev/yocto-slave/nightly-x86/build/b
>>>>>>> ui
>>>>>>> l
>>>>>>>
>>>>>>> d/tmp/work/qemux86-poky-linux/linux-yocto/3.10.25+gitAUTOINC+4d658aa5
>>>>>>> 80
>>>>>>> _
>>>>>>> 78d2a615b1-r0/temp/log.do_compile.1426)
>
> So since this is qemux86 that is failing, and Bruce has run the qemu
> builds - so are we using the right SRCREVs?
>
> Machine: 78d2a615b1
> Meta: 4d658aa580
That's exactly what just popped into my mind. I didn't send updates
for the meta-yocto BSPs with this first change. But the old SRCREVs
should have continued to work .. very odd, I did see generic x86
in the path, so I thought it was something different.
Bruce
>
>>>>>>
>>>>>> This can be seen on the AB
>>>>>>
>>>>>>
>>>>>> http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/2
>>>>>> 0/
>>>>>> s
>>>>>> teps/BuildImages/logs/stdio
>
> --
> Darren
>
>
next prev parent reply other threads:[~2014-02-07 16:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 17:34 [PATCH 0/2] kernel: consolidated pull request Bruce Ashfield
2014-02-04 17:34 ` [PATCH 1/2] kernel: stop using -exec rm for deleting files Bruce Ashfield
2014-02-04 23:26 ` Richard Purdie
2014-02-05 0:35 ` Bruce Ashfield
2014-02-05 1:36 ` Paul Barker
2014-02-05 3:10 ` Bruce Ashfield
2014-02-09 12:06 ` Richard Purdie
2014-02-09 14:36 ` Bruce Ashfield
2014-02-10 13:32 ` Bruce Ashfield
2014-02-10 17:17 ` Bruce Ashfield
2014-02-10 17:23 ` Richard Purdie
2014-02-04 17:34 ` [PATCH 2/2] linux-yocto/3.10: integrate LTSI Bruce Ashfield
2014-02-07 16:42 ` Saul Wold
2014-02-07 16:44 ` Bruce Ashfield
2014-02-07 16:46 ` Darren Hart
2014-02-07 16:47 ` Darren Hart
2014-02-07 16:48 ` Bruce Ashfield
2014-02-07 16:55 ` Darren Hart
2014-02-07 16:57 ` Bruce Ashfield [this message]
2014-02-07 17:24 ` Bruce Ashfield
2014-02-07 17:32 ` Darren Hart
2014-02-07 19:22 ` Bruce Ashfield
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=52F51080.1000808@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=nitin.a.kamble@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=sgw@linux.intel.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