All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [kbuild:kbuild 13/24] fixdep: error opening file: fs/xfs/.xfs_ioctl.o.d: No such file or directory
Date: Sun, 25 Nov 2018 23:50:34 +0900	[thread overview]
Message-ID: <CAK7LNARFoMReFpVnQp+tpfqkE7C_h7_dEoDW7GWYRCdrYhi6_Q@mail.gmail.com> (raw)
In-Reply-To: <201811242107.q8RCw4pQ%fengguang.wu@intel.com>

On Sat, Nov 24, 2018 at 10:13 PM kbuild test robot <lkp@intel.com> wrote:
>
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git kbuild
> head:   9a1006b7aba40da544f7d138c90222b904f5c7ab
> commit: b6062bbfc43f6b217548e76000cf1dd959cff7bb [13/24] kbuild: change if_changed_rule for multi-line recipe
> config: sh-sdk7786_defconfig (attached as .config)
> compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
> reproduce:
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout b6062bbfc43f6b217548e76000cf1dd959cff7bb
>         # save the attached .config to linux build tree
>         GCC_VERSION=7.2.0 make.cross ARCH=sh
>
> Note: the kbuild/kbuild HEAD 9a1006b7aba40da544f7d138c90222b904f5c7ab builds fine.
>       It only hurts bisectibility.


I locally fixed up the kbuild branch
to get back the bisectability.


Thanks for the report.



-- 
Best Regards
Masahiro Yamada

      reply	other threads:[~2018-11-26  1:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24 13:13 [kbuild:kbuild 13/24] fixdep: error opening file: fs/xfs/.xfs_ioctl.o.d: No such file or directory kbuild test robot
2018-11-25 14:50 ` Masahiro Yamada [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=CAK7LNARFoMReFpVnQp+tpfqkE7C_h7_dEoDW7GWYRCdrYhi6_Q@mail.gmail.com \
    --to=yamada.masahiro@socionext.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=lkp@intel.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.