All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Larsen <lars@visionweeding.com>
To: poky@yoctoproject.org
Subject: How to proceed ? I Found an error in pseudo_native that has been corrected in a latter commit
Date: Thu, 5 Jan 2017 13:05:14 +0100	[thread overview]
Message-ID: <586E367A.8070004@visionweeding.com> (raw)

Hello world

We are using Morty branch of Yocto.
I have been compiling a lot on a 64 bit host (Ubuntu -14-04), for a 32 
bit  x86 target , it is working fine.

Now an other team member should build it, he is using an 32 bit host 
(Ubuntu-12-04)
On his machine for some reason,  I don't know why, bitbake decides that 
it needs to build pseudo_native -  and that build fails.

the errors are very basic syntax errors in some python scripts.
and after investigating the repositories for pseudo_native, I see that 
these errors has been fixed in the pseudo_native repository. But in a 
latter commit than the one Morty pulls in.

How do i proceed ?
I can fix the errors locally and make a .bbappend with a patch that 
correct these specific errors, or change the SRCREV.
I'm unsure about  the correct procedure to follow ?
Can anyone guide me gently ??

thanks in advance

-Lars

-- 

Best Regards
Lars Larsen

F.Poulsen Engineering Aps
Tjørnager 16
4330 Hvalsø
Denmark
+45 29802784
www.visionweeding.com



             reply	other threads:[~2017-01-05 12:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 12:05 Lars Larsen [this message]
2017-01-05 13:10 ` How to proceed ? I Found an error in pseudo_native that has been corrected in a latter commit Burton, Ross

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=586E367A.8070004@visionweeding.com \
    --to=lars@visionweeding.com \
    --cc=poky@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.