Re: Problems during compiling in kernel modules

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:44:29 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1909141641270.2490@hadrien> (raw)
In-Reply-To: <20190914143723.GA7704@SARKAR>

On Sat, 14 Sep 2019, Rohit Sarkar wrote:

> On Sat, Sep 14, 2019 at 07:55:27PM +0530, 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
> > `
> >
> > 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?
> >
> > Thanks,
> > Rohit
>
> For reference:
> This is the result of `make drivers/staging/iio/`
> `
>   CALL    scripts/checksyscalls.sh
>   CALL    scripts/atomic/check-atomics.sh
>   DESCEND  objtool
>   AR      drivers/staging/iio/accel/built-in.a
>   AR      drivers/staging/iio/adc/built-in.a
>   AR      drivers/staging/iio/addac/built-in.a
>   AR      drivers/staging/iio/cdc/built-in.a
>   AR      drivers/staging/iio/frequency/built-in.a
>   AR      drivers/staging/iio/impedance-analyzer/built-in.a
>   AR      drivers/staging/iio/meter/built-in.a
>   AR      drivers/staging/iio/resolver/built-in.a
>   AR      drivers/staging/iio/built-in.a

Perhaps you have already compiled the .o files that are used to produce
these .a files?  There seem to be some files that are simply not possible
to compile.  Perhaps they can be compiled for some other architecture.
But you can also just work on the files that you are able to compile.

julia