linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damian Tometzki <linux_dti@icloud.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: kbuild test robot <lkp@intel.com>,
	kbuild-all@01.org, linux-kernel@vger.kernel.org,
	tipbuild@zytor.com, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [tip:locking/core 5/6] /bin/bash: scripts/atomic/check-atomics.sh: No such file or directory
Date: Fri, 02 Nov 2018 14:01:04 +0100	[thread overview]
Message-ID: <20181102130103.GA2064@Ubuntu-DTI> (raw)
In-Reply-To: <20181101112943.4zwlwsmkeebg7p5k@lakrids.cambridge.arm.com>

Hello Mark,

i got now the error:
/bin/bash: scripts/atomic/check-atomics.sh: No such file or directory
make[2]: *** [/home/damian/kernel/linux/./Kbuild:86: old-atomics] Fehler 127
make[1]: *** [/home/damian/kernel/linux/Makefile:1112: prepare0] Fehler 2

Best regards
Damian




On Do, 01. Nov 11:29, Mark Rutland wrote:
> On Thu, Nov 01, 2018 at 06:16:22PM +0800, kbuild test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
> > head:   30bc7baa9de81efc0584b9290ce8040a1130f156
> > commit: 85f8507192fbfb4ad2ac01de879cb50045f4247f [5/6] locking/atomics: Check generated headers are up-to-date
> > config: i386-tinyconfig (attached as .config)
> > compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> > reproduce:
> >         git checkout 85f8507192fbfb4ad2ac01de879cb50045f4247f
> >         # save the attached .config to linux build tree
> >         make ARCH=i386 
> > 
> > All errors (new ones prefixed by >>):
> > 
> > >> /bin/bash: scripts/atomic/check-atomics.sh: No such file or directory
> >    make[2]: *** [old-atomics] Error 127
> >    make[2]: Target '__build' not remade because of errors.
> >    make[1]: *** [prepare0] Error 2
> >    make[1]: Target 'prepare' not remade because of errors.
> >    make: *** [sub-make] Error 2
> 
> It looks like we accidentally dropped execute permissions from the
> scripts when picking them from the list. Locally I get a slightly
> different failure:
> 
>   ALL    scripts/atomic/check-atomics.sh
>   scripts/atomic/check-atomics.sh: line 16: 
>   scripts/atomic/gen-atomic-instrumented.sh: Permission denied
>   warning: include/asm-generic/atomic-instrumented.h is out-of-date.
>   scripts/atomic/check-atomics.sh: line 16: 
>   scripts/atomic/gen-atomic-long.sh: Permission denied
>   warning: include/asm-generic/atomic-long.h is out-of-date.
>   scripts/atomic/check-atomics.sh: line 16: 
>   scripts/atomic/gen-atomic-fallback.sh: Permission denied
>   warning: include/linux/atomic-fallback.h is out-of-date.
> 
> I've sent a patch [1] to fix this.
> 
> Thanks,
> Mark.
> 
> [1] https://lkml.kernel.org/r/20181101112654.55898-1-mark.rutland@arm.com

      reply	other threads:[~2018-11-02 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 10:16 [tip:locking/core 5/6] /bin/bash: scripts/atomic/check-atomics.sh: No such file or directory kbuild test robot
2018-11-01 11:29 ` Mark Rutland
2018-11-02 13:01   ` Damian Tometzki [this message]

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=20181102130103.GA2064@Ubuntu-DTI \
    --to=linux_dti@icloud.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mark.rutland@arm.com \
    --cc=peterz@infradead.org \
    --cc=tipbuild@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).