public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. R. Okajima" <hooanon05g@gmail.com>
To: masahiroy@kernel.org, mcgrof@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: how to build a single module
Date: Mon, 02 Jan 2023 05:06:53 +0900	[thread overview]
Message-ID: <25966.1672603613@jrobl> (raw)

Hello,

In linux-v6.2-rc1, "make brabra/module.ko" to build a single module
doesn't work. It compiles the C source files and produces .o, but the
final 'modpost' returns an error.

$ make fs/aufs/aufs.ko
	:::
  LD [M]  fs/aufs/aufs.o
  MODPOST Module.symvers
ERROR: modpost: fs/aufs/aufs.ko: filename must be suffixed with .o
make[2]: *** [/proj/aufs/aufs6-linux.git/scripts/Makefile.modpost:137: Module.symvers] Error 1
make[1]: *** [/proj/aufs/aufs6-linux.git/Makefile:1996: single_modules] Error 2
make: *** [/proj/aufs/aufs6-linux.git/Makefile:373: __build_one_by_one] Error 2
Command exited with non-zero status 2


Is it related to this commit?
	f65a486821cf 2022-12-14 kbuild: change module.order to list *.o instead of *.ko


J. R. Okajima

             reply	other threads:[~2023-01-01 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-01 20:06 J. R. Okajima [this message]
2023-01-01 20:44 ` how to build a single module Randy Dunlap
2023-01-02  2:30   ` J. R. Okajima

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=25966.1672603613@jrobl \
    --to=hooanon05g@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mcgrof@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