linux-kernel - Re: build failure of next-20220715 due to "No rule to make target"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 15 Jul 2022 21:15:42 -0500
From:   Samuel Holland <samuel@...lland.org>
To:     Florian Fainelli <f.fainelli@...il.com>,
        "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@...il.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Chen-Yu Tsai <wens@...e.org>,
        Jernej Skrabec <jernej.skrabec@...il.com>
Cc:     linux-gpio@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-sunxi@...ts.linux.dev, linux-kernel@...r.kernel.org,
        linux-next@...r.kernel.org
Subject: Re: build failure of next-20220715 due to "No rule to make target"

On 7/15/22 8:59 PM, Florian Fainelli wrote:
> On 7/15/2022 4:35 PM, Sudip Mukherjee (Codethink) wrote:
>> Not sure if it has been reported, builds of arm and arm64 allmodconfig
>> have failed to build next-20220715 with the error:
>>
>> make[3]: *** No rule to make target
>> 'drivers/pinctrl/sunxi/pinctrl-sun20i-d1.o', needed by
>> 'drivers/pinctrl/sunxi/built-in.a'.  Stop.
> 
> Caused by f6e42a0fce98b85380df8cdfb081d75c48e4fee1 ("pinctrl: sunxi: Add driver
> for Allwinner D1/D1s") adding CONFIG_PINCTRL_SUN20I_D1 a build rule in
> drivers/pinctrl/sunxi/Makefile to build pinctrl-sun20i-d1.o but ... there was no
> drivers/pinctrl/sunxi/pinctrl-sun20i-d1.c file added to the commit, missing git
> add presumably?

The patch in question[0] contains the new file, so something must have gone
wrong when applying it[1]. I wasn't sure what to do, so I resent the whole
series[2], in case the index hashes in the v1 patches were causing the problem.

Regards,
Samuel

[0]: https://lore.kernel.org/linux-gpio/20220626021148.56740-7-samuel@sholland.org/
[1]:
https://lore.kernel.org/linux-gpio/879fb3b2-4bcb-82d6-e186-e845d62c9843@sholland.org/
[2]: https://lore.kernel.org/linux-gpio/20220713025233.27248-1-samuel@sholland.org/