From: Nicholas Mc Guire <der.herr@hofr.at>
To: Jefferson Carpenter <jefferson@aoeu2code.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Is there a "build everything" kernel configuration?
Date: Sat, 13 Apr 2019 09:30:49 +0200 [thread overview]
Message-ID: <20190413073049.GA22596@osadl.at> (raw)
In-Reply-To: <16a153637cc.117ac4db3472558.4421794693225896449@aoeu2code.com>
On Fri, Apr 12, 2019 at 10:40:35PM -0700, Jefferson Carpenter wrote:
> Supposing I want to make a change to the Kernel code and make sure that it all builds (i.e. that I did not cause any compile errors under any configuration), what's best way to do that? Can I just take the default setting for all config options or does there exist a "build everything" mode?
>
you can do make allyesconfig which is about as close to build everything
as you can get. Of course this still will only build for one particular
architecture - so to build all architectures you would need to iterate over
ARCH= .
thx!
hofrat
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2019-04-13 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 5:40 Is there a "build everything" kernel configuration? Jefferson Carpenter
2019-04-13 7:30 ` Nicholas Mc Guire [this message]
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=20190413073049.GA22596@osadl.at \
--to=der.herr@hofr.at \
--cc=jefferson@aoeu2code.com \
--cc=kernelnewbies@kernelnewbies.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).