All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: So what happened to Edison??
Date: Mon, 30 Jan 2012 14:55:58 -0800	[thread overview]
Message-ID: <4F271FFE.3050701@linux.intel.com> (raw)
In-Reply-To: <4F271E07.70306@gmail.com>

On 30/01/12 14:47, jfabernathy wrote:
> On 01/30/2012 05:43 PM, Joshua Lock wrote:
>>
>>
>> On 30/01/12 14:33, jfabernathy wrote:
>>> On 01/30/2012 05:12 PM, Joshua Lock wrote:
>>>> On 30/01/12 13:54, jfabernathy wrote:
>>>>> On 01/30/2012 04:51 PM, Bruce Ashfield wrote:
>>>>>> On Mon, Jan 30, 2012 at 4:47 PM, jfabernathy<jfabernathy@gmail.com>
>>>>>> wrote:
>>>>>>> It seems that something happened today. I could not complete a
>>>>>>> build on
>>>>>>> edison branch for meta-cedartrail. I copied it to meta-mycdv, but
>>>>>>> other
>>>>>>> than that same, old same old. I tried the standard unchanged SRCREV
>>>>>>> and
>>>>>>> also tried the latest.
>>>>>> I changed the main yocto 1.2 3.0 kernel repository to 3.0, and pushed
>>>>>> some other kernel
>>>>>> changes. But if you are purely on edison, and aren't using
>>>>>> meta-kernel-dev there
>>>>>> shouldn't have been any fallout from those changes. (I built 3.0
>>>>>> several times today
>>>>>> myself).
>>>>>>
>>>>>> Perhaps Josh knows if anything was pushed to edison ?
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Bruce
>>>>>
>>>>> I'm retesting on the tarballs again. If successful I'll try git
>>>>> version
>>>>> of edison. I started today with complete new clone of poky and
>>>>> meta-intel.
>>>>
>>>> The Edison branch has been updated today for the upcoming 1.1 release,
>>>> did you pull the updates?
>>>>
>>>> Other than meta-intel are you using any other layers? I will try and
>>>> reproduce here.
>>>>
>>>
>>> I tried some stuff this morning like switching branches, then doing git
>>> pulls, etc. I was getting such bad results, I figured I had screwed up.
>>> I re-cloned both poky and meta-intel earlier today. Maybe around 12 noon
>>> EST.
>>
>> This sounds like meta-intel and the Edison updates aren't getting
>> along. Just to clarify are you using the latest poky edison branch?
>> Which meta-intel branch/tag are you using?
>>
> What I did after cloning Poky and Meta-intel, I cheched out edison in
> both poky and meta-intel direction using the same command that they use
> in Developer Manual Appendix A.

Right. I think we'll need to change the manual, at least to make it 
clear that the branches are not static.

As an aside to that I will see if I can figure out what's causing the 
error you reported.

Joshua
-- 
Joshua Lock
         Yocto Project "Johannes factotum"
         Intel Open Source Technology Centre


  reply	other threads:[~2012-01-30 22:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 21:47 So what happened to Edison?? jfabernathy
2012-01-30 21:51 ` Bruce Ashfield
2012-01-30 21:54   ` jfabernathy
2012-01-30 22:12     ` Joshua Lock
2012-01-30 22:33       ` jfabernathy
2012-01-30 22:43         ` Joshua Lock
2012-01-30 22:47           ` jfabernathy
2012-01-30 22:55             ` Joshua Lock [this message]
2012-01-30 22:51           ` jfabernathy
2012-01-31  4:37             ` Joshua Lock

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=4F271FFE.3050701@linux.intel.com \
    --to=josh@linux.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.