From: m silverstri <michael.j.silverstri@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: How to run sparse tool?
Date: Thu, 13 Mar 2014 11:54:13 -0700 [thread overview]
Message-ID: <CABMudhQt1B6kanw+u7A1yPnux-wUYGYq07qwFs4hGYhgdbYLTA@mail.gmail.com> (raw)
In-Reply-To: <20140313180031.GA6144@ravnborg.org>
Thanks. 'make allmodconfig' works.
But before your answer, I am able to build and there is a .config
file. But why 'make C=2 drivers/staging/wlan-ng/' decide to build
config again ?
On Thu, Mar 13, 2014 at 11:00 AM, Sam Ravnborg <sam@ravnborg.org> wrote:
> Hi Michael.
>
> On Thu, Mar 13, 2014 at 09:49:48AM -0700, m silverstri wrote:
>> Hi,
>>
>> I read http://kernelnewbies.org/Sparse and try to run sparse tool.
>>
>> As a test, I run it on raspberry-pi/linux code base, by doing " make
>> C=2 drivers/staging/wlan-ng/", what I get is it asks me a list of
>> configuration question and it does not run sparse for me. How can I
>> bypass this setting up configuration and run sparse for the code?
>
> You cannot build the kernel source before the kernel is properly configured.
> You can use one of the shortcuts if you just want to build test this:
>
> make allyesconfig
>
> or
>
> make allmodconfig
>
> This will configure your kernel and allow you to build the wlan-ng/
> drivers.
> And when you can build the drivers then you can also run sparse.
>
> Sam
next prev parent reply other threads:[~2014-03-13 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 16:49 How to run sparse tool? m silverstri
2014-03-13 18:00 ` Sam Ravnborg
2014-03-13 18:54 ` m silverstri [this message]
2014-03-13 21:23 ` Sam Ravnborg
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=CABMudhQt1B6kanw+u7A1yPnux-wUYGYq07qwFs4hGYhgdbYLTA@mail.gmail.com \
--to=michael.j.silverstri@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sam@ravnborg.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).