All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] make-mod-scripts: Fix a rare build race condition
Date: Wed, 27 May 2020 14:04:53 -0400	[thread overview]
Message-ID: <CADkTA4P2GpH2b_zWCHgyGk-ZCBNxmD2925wR-F6PEMGrPYPU3w@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1sqxekhk7d+tZ8vWJ44haRv801v+ydp9BjhL0+w5M=2h9w@mail.gmail.com>

On Wed, May 27, 2020 at 1:46 PM Khem Raj <raj.khem@gmail.com> wrote:
>
> On Wed, May 27, 2020 at 9:57 AM Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
> >
> > On Wed, May 27, 2020 at 12:03 PM Khem Raj <raj.khem@gmail.com> wrote:
> > >
> > > There is a build break which often happens whem using 4.1 kernel
> > >
> > > /bin/sh: 1: scripts/basic/fixdep: Permission denied
> > > scripts/Makefile.host:124: recipe for target 'scripts/dtc/srcpos.o' failed
> > > make[3]: *** [scripts/dtc/srcpos.o] Error 126
> > >
> > > this patch sequences the build targets so it can work reliably with
> > > different kernel versions
> > >
> > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > > Cc: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > ---
> > >  .../make-mod-scripts/make-mod-scripts_1.0.bb               | 7 ++++---
> > >  1 file changed, 4 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/meta/recipes-kernel/make-mod-scripts/make-mod-scripts_1.0.bb b/meta/recipes-kernel/make-mod-scripts/make-mod-scripts_1.0.bb
> > > index 0be1422a24..c7edb20ee4 100644
> > > --- a/meta/recipes-kernel/make-mod-scripts/make-mod-scripts_1.0.bb
> > > +++ b/meta/recipes-kernel/make-mod-scripts/make-mod-scripts_1.0.bb
> > > @@ -23,7 +23,8 @@ EXTRA_OEMAKE = " HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="
> > >  #
> > >  do_configure() {
> > >         unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS
> > > -       oe_runmake CC="${KERNEL_CC}" LD="${KERNEL_LD}" AR="${KERNEL_AR}" \
> > > -                  -C ${STAGING_KERNEL_DIR} O=${STAGING_KERNEL_BUILDDIR} scripts prepare
> > > -
> > > +       for t in prepare scripts_basic scripts; do
> >
> > Last I checked, we don't actually need scripts_basic.
> >
> > Isn't just sequencing prepare, followed by 'scripts' enough ?
> >
> > If not, we really should put in the long log why we need that new
> > target when sequencing, when we didn't need it before.
> >
>
> in a way you are right that scripts should cover it, but calling it
> out explicitly avoids any weird races if any and it does not
> hurt until this target is removed. I really have not debugged kernel
> build to see what is causing this, so there is not much
> details to add other than this that we are handing some race
> conditions which ideally should be in the makery
>

But the race condition is handled with the two targets, no ? I realize
it doesn't hurt, but you are implying that you need all three to be
sure, but that really isn't the case from what I've seen.

I just think simpler is better, but don't take my comments as an objection.

Cheers,

Bruce

> > Bruce
> >
> > > +               oe_runmake CC="${KERNEL_CC}" LD="${KERNEL_LD}" AR="${KERNEL_AR}" \
> > > +               -C ${STAGING_KERNEL_DIR} O=${STAGING_KERNEL_BUILDDIR} $t
> > > +       done
> > >  }
> > > --
> > > 2.26.2
> > >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

  reply	other threads:[~2020-05-27 18:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 16:03 [PATCH] make-mod-scripts: Fix a rare build race condition Khem Raj
2020-05-27 16:06 ` [OE-core] " Denys Dmytriyenko
2020-05-27 16:56 ` Bruce Ashfield
2020-05-27 17:45   ` Khem Raj
2020-05-27 18:04     ` Bruce Ashfield [this message]
2020-05-27 19:23       ` Khem Raj
2020-05-27 19:34         ` 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=CADkTA4P2GpH2b_zWCHgyGk-ZCBNxmD2925wR-F6PEMGrPYPU3w@mail.gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 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.