From: Jim Abernathy <jfabernathy@gmail.com>
To: Tom Zanussi <tom.zanussi@intel.com>
Cc: yocto@yoctoproject.org, Darren Hart <dvhart@linux.intel.com>
Subject: Re: nothing building under denzil-7.0.1
Date: Fri, 20 Jul 2012 16:42:13 -0400 [thread overview]
Message-ID: <5009C2A5.5050802@gmail.com> (raw)
In-Reply-To: <1342816760.2274.2.camel@trz-ThinkPad-T420>
On 07/20/2012 04:39 PM, Tom Zanussi wrote:
> On Fri, 2012-07-20 at 16:35 -0400, Jim Abernathy wrote:
>> On 07/20/2012 04:29 PM, Scott Garman wrote:
>>> On 07/20/2012 01:11 PM, Jim Abernathy wrote:
>>>> There must be some basic thing I'm missing. Nothing that I used to
>>>> build under denzil 7.0 will now build under denzil 7.0.1 or tracking the
>>>> denzil branch. Are all the BSPs required to be updated to 7.0.1 before
>>>> you can run?
>>>>
>>>> I'd thought I'd check before I post a bunch of log files.
>>>>
>>>> I just downloaded the poky 7.0.1 tarball and cd'ed to that untarred
>>>> directory and untarred the 7.0 Intel BSPs.
>>>>
>>>> There must be a step I'm missing. otherwise this would not have gotten
>>>> thru testing before deployment.
>>>>
>>>> Jim A
>>> Hi Jim,
>>>
>>> We need more specific information about the error(s) you're seeing.
>>> We've done extensive QA with 7.0.1 and meta-intel, so I imagine there
>>> must be a step you've forgotten.
>>>
>>> For example, you are using the denzil branch of meta-intel, right?
>>>
>>> Scott
>>>
>> I think it maybe that old problem with the n450 SRCREC being blank in
>> the linux-yocto bbappend file. Obviously that BSP didn't get fixed
>> before 7.0.1 was deployed. I'll put in the ones I used to patch in and
>> see if it works.
>>
> I updated the n450 in both the denzil and master meta-intel branches,
> but the tarball still needs to be updated with that fix.
>
> Is this the problem you're seeing, or are there other problems you're
> seeing with this and/or the other meta-intel BSPs?
>
> Tom
I should know shortly. I patched the n450 like I did before. I forgot
that BSP didn't get updated when denzil 7.0.1 came out. Duh!
If you have it fixed in Denzil and master branch, I'll test that as well.
>> Jim A
>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2012-07-20 20:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 20:11 nothing building under denzil-7.0.1 Jim Abernathy
2012-07-20 20:29 ` Scott Garman
2012-07-20 20:35 ` Jim Abernathy
2012-07-20 20:39 ` Tom Zanussi
2012-07-20 20:42 ` Jim Abernathy [this message]
2012-07-20 20:48 ` Tom Zanussi
2012-07-20 21:05 ` Darren Hart
2012-07-20 22:12 ` Jim Abernathy
2012-07-20 23:02 ` Darren Hart
2012-07-21 1:08 ` Jim Abernathy
2012-07-20 21:55 ` Tom Zanussi
2012-07-21 4:06 ` Tom Zanussi
2012-07-21 13:58 ` Jim Abernathy
2012-07-21 15:43 ` Jim Abernathy
2012-07-21 23:47 ` Tom Zanussi
2012-07-23 12:18 ` Jim Abernathy
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=5009C2A5.5050802@gmail.com \
--to=jfabernathy@gmail.com \
--cc=dvhart@linux.intel.com \
--cc=tom.zanussi@intel.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.