All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Merging problems
Date: Sat, 20 Dec 2014 22:14:44 +0000	[thread overview]
Message-ID: <1419113684.13316.43.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKpOb_c1ZhF6B5W9DejgTbLtuMVpqCKDVxb=+8muQxVbuQ@mail.gmail.com>

On Sat, 2014-12-20 at 17:19 -0200, Otavio Salvador wrote:
> On Sat, Dec 20, 2014 at 9:15 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > So where are we at?
> ...
> > * there are continuing problems with linux-imx from meta-fsl-arm, I
> >   thought these were addressed but clearly not :(
> 
> I have addressed those:
> 
> commit 150b8fe5fb428f9d62b8d5e589ba50bcb64bdb6a (HEAD,
> yocto/master-next, pending)
> Author: Otavio Salvador <otavio@ossystems.com.br>
> Date:   Sat Dec 20 17:11:24 2014 -0200
> 
>     fsl-kernel-localversion.bbclass: Fix building using out-of-tree
> 
>     Since OE-Core:df9975f4 (kernel: Fix non linux-yocto builds) the way
>     the build of kernel is done has change. Now the source code is moved
>     placed at STAGING_KERNEL_DIR and the build is done at ${WORKDIR}/build
>     which is B.
> 
>     This patch adapts the configure task prepending to cope with those changes.
> 
>     Change-Id: I9ea4254ffd56e4b7201daf9a90b52756a399c0f6
>     Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

I had tweaked kernel.bbclass so you shouldn't need to do that, the
system notices if a kernel is configured in ${S} and moves the
configuration to ${B}. I also fixed some other race issues which were
leading to the makefile problems on older autobuilders.

> This is under meta-fsl-arm master-next branch so people give it a go
> in AB and let me know about any other issue you have.

https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm-lsb/builds/131/steps/BuildImages/logs/stdio

Is the latest failure (fsl-arm built ok), I think this may be a parallel
make race?

Cheers,

Richard





  reply	other threads:[~2014-12-20 22:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19 10:28 Merging problems Richard Purdie
2014-12-19 12:41 ` Richard Purdie
2014-12-19 13:07   ` Bruce Ashfield
2014-12-19 13:14     ` Bruce Ashfield
2014-12-19 13:15     ` Richard Purdie
2014-12-19 13:58       ` Bruce Ashfield
2014-12-20 11:15       ` Richard Purdie
2014-12-20 15:13         ` Bruce Ashfield
2014-12-20 22:17           ` Richard Purdie
2014-12-20 22:40           ` Richard Purdie
2014-12-21  2:04             ` Bruce Ashfield
2014-12-21 11:27               ` Richard Purdie
2014-12-21 12:35                 ` Richard Purdie
2014-12-21 13:56                   ` Richard Purdie
2014-12-22  3:40                   ` Bruce Ashfield
2014-12-22  3:38                 ` Bruce Ashfield
2014-12-20 19:19         ` Otavio Salvador
2014-12-20 22:14           ` Richard Purdie [this message]
2014-12-22 16:50         ` Martin Jansa
2014-12-22 17:00           ` Richard Purdie

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=1419113684.13316.43.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.