linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Aurabind <jay.aurabind@gmail.com>
To: Rohit Sarkar <rohitsarkar5398@gmail.com>
Cc: 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 10:27:54 +0530	[thread overview]
Message-ID: <CAOsEZoht6hWU1_pBp-GaRsNSDVj6D+vz0Z9MZRRVqR-HZgJoGg@mail.gmail.com> (raw)
In-Reply-To: <20190913180103.GB5986@SARKAR>

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.

On Sat, 14 Sep 2019 at 00:58, Rohit Sarkar <rohitsarkar5398@gmail.com> wrote:
>
> On Fri, Sep 13, 2019 at 11:08:21PM +0530, Rohit Sarkar wrote:
> > Hi,
> > I was trying to compile a particular folder in my kernel tree.
> >
> > AFAIK the way to do this is:
> > `make drivers/staging/iio/` from the kernel base directory.
> >
> > This gives me the following output:
> > `
> >   CALL    scripts/checksyscalls.sh
> >   CALL    scripts/atomic/check-atomics.sh
> >   DESCEND  objtool
> > `
> >
> > No object files are generated.
> > I feel like I am missing something.
> >
> > Thanks,
> > Rohit
>
> I ran `make clean` in the `drivers/iio/accel` directory which removed
> all object files in the first place. However running make after that
> doesnt seem to compile the modules.
>
> Thanks,
> Rohit



-- 

Thanks and Regards,
Jay

  parent reply	other threads:[~2019-09-14  4:58 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 [this message]
2019-09-14  5:57     ` Julia Lawall
2019-09-14 14:25       ` Rohit Sarkar
2019-09-14 14:35         ` Julia Lawall
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=CAOsEZoht6hWU1_pBp-GaRsNSDVj6D+vz0Z9MZRRVqR-HZgJoGg@mail.gmail.com \
    --to=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).