From: Julia Lawall <julia.lawall@lip6.fr>
To: Rohit Sarkar <rohitsarkar5398@gmail.com>
Cc: Jay Aurabind <jay.aurabind@gmail.com>,
linux-newbie@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: Problems during compiling in kernel modules
Date: Sat, 14 Sep 2019 16:35:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1909141632100.2490@hadrien> (raw)
In-Reply-To: <20190914142527.GA4158@SARKAR>
On Sat, 14 Sep 2019, Rohit Sarkar wrote:
> On Sat, Sep 14, 2019 at 07:57:48AM +0200, Julia Lawall wrote:
> >
> >
> > On Sat, 14 Sep 2019, Jay Aurabind wrote:
> >
> > > Hi Rohit,
> > >
> > > The required config options need to the objects in that folder to be
> > > build. Apparently there is no way to automatically set the required
> > > configs. You can look at the Kconfig files inside drivers/iio/accel
> > > and see what are the dependencies for building various drivers.
> >
> > It looks like some of the drivers are individual files. So you can also
> > just compile them one at a time make staging/drivers.iio/accel/foo.o.
> >
> > julia
> >
>
> Hey julia,
> I ran a `make clean` on that directory by mistake which I realised I
> shouldn't have done. Hence no object files are there.
>
> Giving me this:
>
> `
> make drivers/staging/iio/adis16240.o staging/git/remove-include
> CALL scripts/checksyscalls.sh
> CALL scripts/atomic/check-atomics.sh
> DESCEND objtool
> make[1]: *** No rule to make target 'drivers/staging/iio/adis16240.o'. Stop.
> Makefile:1772: recipe for target 'drivers/staging/iio/adis16240.o' failed
> make: *** [drivers/staging/iio/adis16240.o] Error 2
> `
OK
> I guess I will have to enable `CONFIG_IIO` and rebuild?
> Although what I don't understand is if `CONFIG_IIO` was not enabled how
> were there object files in the first place?
Perhaps the build system is just not very well designed here.
However, for me
make allyesconfig
make drivers/staging/iio/
works, and after that it is possible to do:
make drivers/staging/iio/accel/adis16203.o
I didn't do anything explicitly with CONFIG_IIO.
julia
next prev parent reply other threads:[~2019-09-14 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190913173821.GA5986@SARKAR>
2019-09-13 18:01 ` Problems during compiling in kernel modules Rohit Sarkar
2019-09-13 22:36 ` Randy Dunlap
2019-09-14 6:31 ` Rohit Sarkar
2019-09-14 15:23 ` Randy Dunlap
2019-09-14 4:57 ` Jay Aurabind
2019-09-14 5:57 ` Julia Lawall
2019-09-14 14:25 ` Rohit Sarkar
2019-09-14 14:35 ` Julia Lawall [this message]
2019-09-14 14:45 ` Rohit Sarkar
2019-09-14 15:01 ` Randy Dunlap
2019-09-14 14:37 ` Rohit Sarkar
2019-09-14 14:44 ` Julia Lawall
2019-09-14 9:55 ` Austin Kim
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=alpine.DEB.2.21.1909141632100.2490@hadrien \
--to=julia.lawall@lip6.fr \
--cc=jay.aurabind@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=rohitsarkar5398@gmail.com \
/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).