kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Out-of-tree module build in a dedicated build directory.
Date: Thu, 15 Mar 2018 18:14:59 +0100	[thread overview]
Message-ID: <20180315171459.GB17468@kroah.com> (raw)
In-Reply-To: <CAA181pyU6u4RReHTWZwFiqOTEr2-G7EwN=PzXZvn1S9aFajXLA@mail.gmail.com>

On Thu, Mar 15, 2018 at 05:39:36PM +0100, Aleksei Fedotov wrote:
> > If for some reason make modules did not create module.symvers then try:
> >
> >         cd /home/lexa/linux
> >         make
> >         [wait a few minutes as it builds some scripts and starts building kernel code...]
> >         hit <Ctrl-C>
> >
> > then go back and try building your module.
> 
> But i have my kernel completely build, including kernel modules.
> 
> I get the error about ./Module.symvers only if I specify
> O=module_build_directory. When I build the module without O= there is
> not such error, but the object files are created in the same directory
> as module source, which I want to avoid.

You have to do 'make module_prepare' with your 'O=' set correctly as
well, otherwise how will the build system know where to look for the
object files to link/build against?

thanks,

greg k-h

  reply	other threads:[~2018-03-15 17:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 12:14 Out-of-tree module build in a dedicated build directory Aleksei Fedotov
2018-03-15 13:00 ` Greg KH
2018-03-15 13:33   ` Aleksei Fedotov
2018-03-15 13:36     ` Denis Kirjanov
2018-03-15 14:01     ` Greg KH
2018-03-15 14:36       ` Aleksei Fedotov
2018-03-15 14:52         ` Aruna Hewapathirane
2018-03-15 15:27           ` Aruna Hewapathirane
2018-03-15 16:26             ` Greg KH
2018-03-15 16:39               ` Aleksei Fedotov
2018-03-15 17:14                 ` Greg KH [this message]
2018-03-15 18:58                 ` Aruna Hewapathirane

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=20180315171459.GB17468@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).