All of lore.kernel.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: guoren@kernel.org
Cc: nathan@kernel.org, naresh.kamboju@linaro.org,
	linux-next@vger.kernel.org,  linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org, lkft-triage@lists.linaro.org,
	 regressions@lists.linux.dev,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	guoren@linux.alibaba.com, heiko@sntech.de,
	Arnd Bergmann <arnd@arndb.de>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	aou@eecs.berkeley.edu
Subject: Re: [next] riscv: Linux next-20220404 riscv defconfig builds failed.
Date: Tue, 05 Apr 2022 09:15:01 -0700 (PDT)	[thread overview]
Message-ID: <mhng-cfa7bfb9-bab8-423c-85ad-ecd407d6e806@palmer-ri-x1c9> (raw)
In-Reply-To: <CAJF2gTQkGZnwXrXsbx8drL0AicVpOMW=JmOcrieuvyEf91XPhg@mail.gmail.com>

On Mon, 04 Apr 2022 22:17:24 PDT (-0700), guoren@kernel.org wrote:
> On Tue, Apr 5, 2022 at 12:57 AM Nathan Chancellor <nathan@kernel.org> wrote:
>>
>> On Mon, Apr 04, 2022 at 03:28:41PM +0530, Naresh Kamboju wrote:
>> > Linux next-20220404 riscv defconfig builds failed.
>> >
>> > Regressions found on riscv:
>> >    - riscv-riscv-clang-14-defconfig
>> >    - riscv-riscv-gcc-10-defconfig
>> >    - riscv-riscv-clang-13-defconfig
>> >    - riscv-riscv-clang-12-defconfig
>> >    - riscv-riscv-clang-11-defconfig
>> >    - riscv-riscv-gcc-11-defconfig
>> >    - riscv-riscv-gcc-8-defconfig
>> >    - riscv-riscv-gcc-9-defconfig
>> >    - riscv-riscv-clang-nightly-defconfig
>> >
>> >
>> > arch/riscv/kernel/compat_signal.c:7:10: fatal error:
>> > linux/tracehook.h: No such file or directory
>> >   7 | #include <linux/tracehook.h>
>> >     |          ^~~~~~~~~~~~~~~~~~~
>> > compilation terminated.
>> > make[3]: *** [scripts/Makefile.build:289:
>> > arch/riscv/kernel/compat_signal.o] Error 1
>>
>> For what it's worth, I also see:
>>
>> $ make -skj"$(nproc)" ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- defconfig all
>> arch/riscv/kernel/compat_vdso/compat_vdso.lds.S:3:10: fatal error: ../vdso/vdso.lds.S: No such file or directory
>>     3 | #include <../vdso/vdso.lds.S>
>>       |          ^~~~~~~~~~~~~~~~~~~~
>> compilation terminated.
>> make[2]: *** [scripts/Makefile.build:462: arch/riscv/kernel/compat_vdso/compat_vdso.lds] Error 1
>> arch/riscv/kernel/compat_vdso/rt_sigreturn.S:3:10: fatal error: ../vdso/rt_sigreturn.S: No such file or directory
>>     3 | #include <../vdso/rt_sigreturn.S>
>>       |          ^~~~~~~~~~~~~~~~~~~~~~~~
>> compilation terminated.
>> arch/riscv/kernel/compat_vdso/note.S:3:10: fatal error: ../vdso/note.S: No such file or directory
>>     3 | #include <../vdso/note.S>
>>       |          ^~~~~~~~~~~~~~~~
>> compilation terminated.
>> arch/riscv/kernel/compat_vdso/getcpu.S:3:10: fatal error: ../vdso/getcpu.S: No such file or directory
>>     3 | #include <../vdso/getcpu.S>
>>       |          ^~~~~~~~~~~~~~~~~~
>> compilation terminated.
>> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/rt_sigreturn.o] Error 1
>> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/note.o] Error 1
>> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/getcpu.o] Error 1
>> arch/riscv/kernel/compat_vdso/flush_icache.S:3:10: fatal error: ../vdso/flush_icache.S: No such file or directory
>>     3 | #include <../vdso/flush_icache.S>
>>       |          ^~~~~~~~~~~~~~~~~~~~~~~~
>> compilation terminated.
>> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/flush_icache.o] Error 1
>>
>> I am guessing this code was never tested with $(srctree) == $(objtree).
> Thx for pointing it out:
> I always use:
> make -skj"$(nproc)" ARCH=riscv
> CROSS_COMPILE=riscv64-unknown-linux-gnu- EXTRA_CFLAGS+=-g
> O=../build-riscv/ defconfig all
>
> When I change to:
> make -skj"$(nproc)" ARCH=riscv
> CROSS_COMPILE=riscv64-unknown-linux-gnu- EXTRA_CFLAGS+=-g defconfig
> all
>
> I got your problem.

Just to be clear: this one wasn't supposed to go in via the csky tree, 
and had other build issues that were being found by the autobuilders 
(which is why it hadn't gone in via the riscv tree).  I do in-tree 
builds somewhat regularly so that probably would have caught it if 
nothing else did, but my guess is that some other autobuilder would have 
found it first (some of the earlier patches 

Guo: please stop pushing things to linux-next that break the builds 
and/or aren't aimed at your tree.  This just makes things unnecessarly 
complicated.  If you don't want to deal with the build issues that's OK, 
just LMK when you send the patch sets out and I'll deal with them, but 
having linux-next's build break causes fallout for a lot of users.

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@rivosinc.com>
To: guoren@kernel.org
Cc: nathan@kernel.org, naresh.kamboju@linaro.org,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org, lkft-triage@lists.linaro.org,
	regressions@lists.linux.dev,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	guoren@linux.alibaba.com, heiko@sntech.de,
	Arnd Bergmann <arnd@arndb.de>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	aou@eecs.berkeley.edu
Subject: Re: [next] riscv: Linux next-20220404 riscv defconfig builds failed.
Date: Tue, 05 Apr 2022 09:15:01 -0700 (PDT)	[thread overview]
Message-ID: <mhng-cfa7bfb9-bab8-423c-85ad-ecd407d6e806@palmer-ri-x1c9> (raw)
In-Reply-To: <CAJF2gTQkGZnwXrXsbx8drL0AicVpOMW=JmOcrieuvyEf91XPhg@mail.gmail.com>

On Mon, 04 Apr 2022 22:17:24 PDT (-0700), guoren@kernel.org wrote:
> On Tue, Apr 5, 2022 at 12:57 AM Nathan Chancellor <nathan@kernel.org> wrote:
>>
>> On Mon, Apr 04, 2022 at 03:28:41PM +0530, Naresh Kamboju wrote:
>> > Linux next-20220404 riscv defconfig builds failed.
>> >
>> > Regressions found on riscv:
>> >    - riscv-riscv-clang-14-defconfig
>> >    - riscv-riscv-gcc-10-defconfig
>> >    - riscv-riscv-clang-13-defconfig
>> >    - riscv-riscv-clang-12-defconfig
>> >    - riscv-riscv-clang-11-defconfig
>> >    - riscv-riscv-gcc-11-defconfig
>> >    - riscv-riscv-gcc-8-defconfig
>> >    - riscv-riscv-gcc-9-defconfig
>> >    - riscv-riscv-clang-nightly-defconfig
>> >
>> >
>> > arch/riscv/kernel/compat_signal.c:7:10: fatal error:
>> > linux/tracehook.h: No such file or directory
>> >   7 | #include <linux/tracehook.h>
>> >     |          ^~~~~~~~~~~~~~~~~~~
>> > compilation terminated.
>> > make[3]: *** [scripts/Makefile.build:289:
>> > arch/riscv/kernel/compat_signal.o] Error 1
>>
>> For what it's worth, I also see:
>>
>> $ make -skj"$(nproc)" ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- defconfig all
>> arch/riscv/kernel/compat_vdso/compat_vdso.lds.S:3:10: fatal error: ../vdso/vdso.lds.S: No such file or directory
>>     3 | #include <../vdso/vdso.lds.S>
>>       |          ^~~~~~~~~~~~~~~~~~~~
>> compilation terminated.
>> make[2]: *** [scripts/Makefile.build:462: arch/riscv/kernel/compat_vdso/compat_vdso.lds] Error 1
>> arch/riscv/kernel/compat_vdso/rt_sigreturn.S:3:10: fatal error: ../vdso/rt_sigreturn.S: No such file or directory
>>     3 | #include <../vdso/rt_sigreturn.S>
>>       |          ^~~~~~~~~~~~~~~~~~~~~~~~
>> compilation terminated.
>> arch/riscv/kernel/compat_vdso/note.S:3:10: fatal error: ../vdso/note.S: No such file or directory
>>     3 | #include <../vdso/note.S>
>>       |          ^~~~~~~~~~~~~~~~
>> compilation terminated.
>> arch/riscv/kernel/compat_vdso/getcpu.S:3:10: fatal error: ../vdso/getcpu.S: No such file or directory
>>     3 | #include <../vdso/getcpu.S>
>>       |          ^~~~~~~~~~~~~~~~~~
>> compilation terminated.
>> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/rt_sigreturn.o] Error 1
>> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/note.o] Error 1
>> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/getcpu.o] Error 1
>> arch/riscv/kernel/compat_vdso/flush_icache.S:3:10: fatal error: ../vdso/flush_icache.S: No such file or directory
>>     3 | #include <../vdso/flush_icache.S>
>>       |          ^~~~~~~~~~~~~~~~~~~~~~~~
>> compilation terminated.
>> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/flush_icache.o] Error 1
>>
>> I am guessing this code was never tested with $(srctree) == $(objtree).
> Thx for pointing it out:
> I always use:
> make -skj"$(nproc)" ARCH=riscv
> CROSS_COMPILE=riscv64-unknown-linux-gnu- EXTRA_CFLAGS+=-g
> O=../build-riscv/ defconfig all
>
> When I change to:
> make -skj"$(nproc)" ARCH=riscv
> CROSS_COMPILE=riscv64-unknown-linux-gnu- EXTRA_CFLAGS+=-g defconfig
> all
>
> I got your problem.

Just to be clear: this one wasn't supposed to go in via the csky tree, 
and had other build issues that were being found by the autobuilders 
(which is why it hadn't gone in via the riscv tree).  I do in-tree 
builds somewhat regularly so that probably would have caught it if 
nothing else did, but my guess is that some other autobuilder would have 
found it first (some of the earlier patches 

Guo: please stop pushing things to linux-next that break the builds 
and/or aren't aimed at your tree.  This just makes things unnecessarly 
complicated.  If you don't want to deal with the build issues that's OK, 
just LMK when you send the patch sets out and I'll deal with them, but 
having linux-next's build break causes fallout for a lot of users.

  reply	other threads:[~2022-04-05 16:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  9:58 [next] riscv: Linux next-20220404 riscv defconfig builds failed Naresh Kamboju
2022-04-04  9:58 ` Naresh Kamboju
2022-04-04 10:28 ` Guo Ren
2022-04-04 10:28   ` Guo Ren
2022-04-04 16:57 ` Nathan Chancellor
2022-04-04 16:57   ` Nathan Chancellor
2022-04-05  5:17   ` Guo Ren
2022-04-05  5:17     ` Guo Ren
2022-04-05 16:15     ` Palmer Dabbelt [this message]
2022-04-05 16:15       ` Palmer Dabbelt
2022-04-06  1:13       ` Guo Ren
2022-04-06  1:13         ` Guo Ren
2022-04-06  1:32         ` Guo Ren
2022-04-06  1:32           ` Guo Ren

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=mhng-cfa7bfb9-bab8-423c-85ad-ecd407d6e806@palmer-ri-x1c9 \
    --to=palmer@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=guoren@kernel.org \
    --cc=guoren@linux.alibaba.com \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=nathan@kernel.org \
    --cc=paul.walmsley@sifive.com \
    --cc=regressions@lists.linux.dev \
    --cc=sfr@canb.auug.org.au \
    /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.