From: Salvatore Bonaccorso <carnil@debian.org>
To: Steve French <smfrench@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Jessica Yu <jeyu@kernel.org>, Will Deacon <will@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: Ubuntu mainline kernel builds now failing not able to find module.lds file
Date: Wed, 25 Nov 2020 07:01:24 +0100 [thread overview]
Message-ID: <20201125060124.GA25831@lorien.valinor.li> (raw)
In-Reply-To: <CAH2r5msNpjEaBV2er7anqRsDE-9vYRZnsDif0+odOJAYL_aV6w@mail.gmail.com>
Hi Steve,
On Fri, Oct 30, 2020 at 12:43:24AM -0500, Steve French wrote:
> I typically build cifs.ko for testing using the latest Ubuntu mainline
> build - but building a module in the 5.10-rc1 kernel - while booted to
> the 5.10-rc1 ubuntu mainlinekerel - e.g. "make C=1 -C
> /usr/src/linux-headers-`uname -r` M=`pwd` modules
> CF=-D__CHECK_ENDIAN__"
> which has worked for years - no longer works.
>
> make: Entering directory '/usr/src/linux-headers-5.10.0-051000rc1-generic'
> make[2]: *** No rule to make target 'scripts/module.lds', needed by
> '/home/smfrench/cifs-2.6/fs/cifs/cifs.ko'. Stop.
> make[1]: *** [scripts/Makefile.modpost:117: __modpost] Error 2
> make: *** [Makefile:1703: modules] Error 2
> make: Leaving directory '/usr/src/linux-headers-5.10.0-051000rc1-generic'
>
> I don't see a file in scripts/module.lds in
> /usr/src/linux-headers-5.10.0-051000rc1-generic/scripts directory
>
> copying from scripts/module.lds in the 5.10-rc1 git tree to
> /usr/src/linux-headers-5.10.0-051000rc1-generic/scripts fixed the
> problem but was wondering if this is just a packaging problem with
> Ubuntu (missing a file in the kernel headers package for their
> mainline daily builds?)
There is 596b0474d3d9 ("kbuild: preprocess module linker script") in
v5.10-rc1 causing this. So likely the packaging will need some
adjustment to cope with that change?
Have you by chance verified it is not a problem with the upstream
targets?
Regards,
Salvatore
next prev parent reply other threads:[~2020-11-25 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 5:43 Ubuntu mainline kernel builds now failing not able to find module.lds file Steve French
2020-11-25 6:01 ` Salvatore Bonaccorso [this message]
2020-11-25 8:47 ` Jessica Yu
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=20201125060124.GA25831@lorien.valinor.li \
--to=carnil@debian.org \
--cc=geert@linux-m68k.org \
--cc=jeyu@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=palmerdabbelt@google.com \
--cc=smfrench@gmail.com \
--cc=will@kernel.org \
/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