From: Marian Marinov <mm-l@yuhu.biz>
To: Derek Cheugn <rcheng881@student.glendale.edu>,
linux-config@vger.kernel.org
Subject: Re: what's the fast way to enable a config item?
Date: Tue, 05 Jan 2016 12:27:05 +0200 [thread overview]
Message-ID: <568B9A79.8020105@yuhu.biz> (raw)
In-Reply-To: <20151225013040.GA21467@ubuntu-gnome>
You simply need to enable it in your .config file and rebuild.
Marian
On 12/25/2015 03:30 AM, Derek Cheugn wrote:
> hi all,
>
> I have a simple question (have searched but didn't get any good answer
> yet):
>
> what's the best way to enable a config item without interactive
> interface? if I know the module name, I can find the CONFIG_ name by
> this: then in menuconfig to search SENSORS_APPLESMC to enable it;
>
> $ find -name Makefile |xargs grep -w applesmc
> ./drivers/hwmon/Makefile:obj-$(CONFIG_SENSORS_APPLESMC) += applesmc.o
>
> but is there a good way to enable it without interactive interface?
>
> the interactive config interfaces (menuconfig/gconfig/xconfig) are good
> for one or two configs, but when I want to enable a list of modules,
> this solution is not scalable;
>
> I've tried localmodconfig with LSMOD= env variable, but the
> localmodconfig doesn't seem to be working in this way, I feel it's
> working by an elimination way, to start from a known to be working
> config (maybe from a distro or somewhere)
>
> $ LSMOD=~/tmp/modules-merged make localmodconfig
>
> while, I want to start with `make defconfig` and enable a list of config
> needed; that to accept a list of CONFIG_* names, or a list of modules
> name, does anyone if such a config method exists?
>
>
> thanks,
> --
> To unsubscribe from this list: send the line "unsubscribe linux-config" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2016-01-05 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 1:30 what's the fast way to enable a config item? Derek Cheugn
2016-01-05 10:27 ` Marian Marinov [this message]
2016-01-05 21:06 ` Derek Cheugn
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=568B9A79.8020105@yuhu.biz \
--to=mm-l@yuhu.biz \
--cc=linux-config@vger.kernel.org \
--cc=rcheng881@student.glendale.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.