Re: linux-next: build failure after merge of the kbuild tree

Hi Stephen, On Mon, Feb 22, 2021 at 6:33 AM Stephen Rothwell wrote: > > Hi all, > > After merging the kbuild tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > cc1: fatal error: FORCE: No such file or directory > compilation terminated. > > Presuably caused by commit > >

Re: linux-next: build failure after merge of the kbuild tree

Hi Stephen, On Mon, Jul 13, 2020 at 10:56 AM Stephen Rothwell wrote: > > Hi all, > > On Tue, 7 Jul 2020 17:07:20 +1000 Stephen Rothwell > wrote: > > > > Hi all, > > > > After merging the kbuild tree, today's linux-next build (powerpc > > ppc44x_defconfig) failed like this: > > > > cc1: fatal er

Re: linux-next: build failure after merge of the kbuild tree

Hi all, On Tue, 7 Jul 2020 17:07:20 +1000 Stephen Rothwell wrote: > > Hi all, > > After merging the kbuild tree, today's linux-next build (powerpc > ppc44x_defconfig) failed like this: > > cc1: fatal error: opening output file > arch/powerpc/boot/dts/.ebony.dtb.dts.tmp: No such file or direct

Re: linux-next: build failure after merge of the kbuild tree

Hi Masahiro, On Tue, 16 Jul 2019 13:59:51 +0900 Masahiro Yamada wrote: > > For the build error, I will fix it as follows for tomorrow's linux-next: Thanks for the quick response. -- Cheers, Stephen Rothwell pgpN0tCgezN6c.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the kbuild tree

Hi Stephen, On Tue, Jul 16, 2019 at 1:31 PM Stephen Rothwell wrote: > > Hi all, > > After merging the kbuild tree, today's linux-next build (x86_64 > allnoconfig) failed like this: > > make[1]: *** No rule to make target 'modules.order', needed by > 'autoksyms_recursive'. Stop. > > Starting wit

Re: linux-next: build failure after merge of the kbuild tree

Hi Michael, On Sat, Jul 6, 2019 at 9:05 AM Michael Kelley wrote: > > From: Stephen Rothwell Sent: Friday, July 5, 2019 > 1:31 AM > > > > After merging the kbuild tree, today's linux-next build (powerpc > > allyesconfig) failed like this: > > > > In file included from : > > include/clocksource/

RE: linux-next: build failure after merge of the kbuild tree

From: Stephen Rothwell Sent: Friday, July 5, 2019 1:31 AM > > After merging the kbuild tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > In file included from : > include/clocksource/hyperv_timer.h:18:10: fatal error: asm/mshyperv.h: No > such file or > directory >

Re: linux-next: build failure after merge of the kbuild tree

Hi Stephen, 2018-08-23 7:35 GMT+09:00 Stephen Rothwell : > Hi Masahiro, > > After merging the kbuild tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > ld: failed to merge target specific data of file drivers/input/mouse/alps.o > ld: drivers/input/mouse/byd.o: compile

Re: linux-next: build failure after merge of the kbuild tree

2018-05-30 10:29 GMT+09:00 Stephen Rothwell : > Hi Masahiro, > > After merging the kbuild tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > make was continually spawning test compiles. > > I used the kbuild tree from next-20180529 for today. > > A (partial) strace see

Re: linux-next: build failure after merge of the kbuild tree

Stephen, 2018-05-16 16:26 GMT+09:00 Stephen Rothwell : > Hi Masahiro, > > On Wed, 16 May 2018 15:01:38 +0900 Masahiro Yamada > wrote: >> >> How should I handle your fix-up? >> >> May I squash into the original one if you ack to do it, >> or is it better to keep it as a separate patch? > > Either

Re: linux-next: build failure after merge of the kbuild tree

Hi Masahiro, On Wed, 16 May 2018 15:01:38 +0900 Masahiro Yamada wrote: > > How should I handle your fix-up? > > May I squash into the original one if you ack to do it, > or is it better to keep it as a separate patch? Either way is fine by me, but the former reduces the bisection gap. So it d

Re: linux-next: build failure after merge of the kbuild tree

Stephen, 2018-05-15 14:50 GMT+09:00 Stephen Rothwell : > Hi Masahiro, > > After merging the kbuild tree, today's linux-next build (x86_64 > modules_install) failed like this: > > Usage: scripts/depmod.sh /sbin/depmod > Makefile:1314: recipe for target '_modinst_post' failed > > Caused by commit

Re: linux-next: build failure after merge of the kbuild tree

Hi Stephen, 2018-03-29 6:58 GMT+09:00 Stephen Rothwell : > Hi Masahiro, > > After merging the kbuild tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > net/ipv4/netfilter/nf_nat_snmp_basic_main.c:57:10: fatal err > or: nf_nat_snmp_basic.asn1.h: No such file or directory >

Re: linux-next: build failure after merge of the kbuild tree

On 2016-09-15 08:08, Stephen Rothwell wrote: > Hi all, > > After merging the dax-misc tree, today's linux-next build (powerpc > ppc44x_defconfig) failed like this: > > arch/powerpc/kernel/built-in.o: In function `__ksymtab_clear_pages': > (___ksymtab+clear_pages+0x0): undefined reference to `clea

Re: linux-next: build failure after merge of the kbuild tree

Stephen Rothwell writes: > Hi Michal, > > After merging the kbuild tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > ... > arch/powerpc/mm/hash_utils_64.c:929:10: note: in expansion of macro > 'IS_ENABLED' > else if IS_ENABLED(CONFIG_PPC_NATIVE) > ^ > cc1

Re: linux-next: build failure after merge of the kbuild tree

On 2016-03-16 12:29, Stephen Rothwell wrote: > Hi Michal, > > On Wed, 16 Mar 2016 08:56:50 +0100 Michal Marek wrote: >> >> Right. Stephen, could you perhaps move the kbuild tree down in your list >> a bit, so that the fixes are present? > > Done. > > Now you just need to make sure Linus gets th

Re: linux-next: build failure after merge of the kbuild tree

Hi Michal, On Wed, 16 Mar 2016 08:56:50 +0100 Michal Marek wrote: > > Right. Stephen, could you perhaps move the kbuild tree down in your list > a bit, so that the fixes are present? Done. Now you just need to make sure Linus gets them in the right order :-) -- Cheers, Stephen Rothwell

Re: linux-next: build failure after merge of the kbuild tree

On 2016-03-16 08:53, Daniel Wagner wrote: > Hi, > > On 03/16/2016 12:58 AM, Stephen Rothwell wrote: >> After merging the kbuild tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> drivers/gpu/drm/gma500/mdfld_dsi_output.c:407:39: error: initialization from >> incompati

Re: linux-next: build failure after merge of the kbuild tree

Hi, On 03/16/2016 12:58 AM, Stephen Rothwell wrote: > After merging the kbuild tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/gpu/drm/gma500/mdfld_dsi_output.c:407:39: error: initialization from > incompatible pointer type [-Werror=incompatible-pointer-types

Re: linux-next: build failure after merge of the kbuild tree

On 25.2.2013 11:58, Stephen Rothwell wrote: > -- > $ ls -l /bin/sh > lrwxrwxrwx 1 root root 4 Jul 7 2010 /bin/sh -> bash > $ bash --version > GNU bash, version 4.2.20(1)-release (x86_64-pc-linux-gnu) [...] > But bash in sh mode d

Re: linux-next: build failure after merge of the kbuild tree

On Mon, 25 Feb 2013 21:58:45 +1100 Stephen Rothwell wrote: > > But bash in sh mode does not work: The bash manual says: . filename [arguments] source filename [arguments] Read and execute commands from filename in the current shell environment and

Re: linux-next: build failure after merge of the kbuild tree

Hi Michal, On Mon, 25 Feb 2013 11:28:40 +0100 Michal Marek wrote: > > On 25.2.2013 00:56, Stephen Rothwell wrote: > > > > After merging the kbuild tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > scripts/link-vmlinux.sh: line 135: .: .config: file not found

Re: linux-next: build failure after merge of the kbuild tree

On 25.2.2013 00:56, Stephen Rothwell wrote: > Hi Michal, > > After merging the kbuild tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > scripts/link-vmlinux.sh: line 135: .: .config: file not found > > Presumably caused by commit 03b25b47e0f4 ("scripts/link-vmlinux