From: "Kok, Auke" <sofar@foo-projects.org>
To: Martin Christoph <mail@da7a.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.6.21 - "make modules" with GREP_OPTIONS="-C1" (and other)
Date: Wed, 16 May 2007 21:24:53 -0700 [thread overview]
Message-ID: <464BD915.7090209@foo-projects.org> (raw)
In-Reply-To: <464BCB66.2090205@da7a.de>
Martin Christoph wrote:
> [1] Summary:
> If i have some GREP_OPTIONS set (like -C1 or other) i get several errors
> while trying to do "make modules".
>
> [2] Full description:
> With some GREP_OPTIONS set "make modules" drops several errors like that:
>
> root@spot /usr/src/linux # GREP_OPTIONS="-C1" make modules
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> Building modules, stage 2.
> [...]
> WARNING: "aes_enc_blk" [arch/i386/crypto/aes.ko] undefined!
> WARNING: "aes_dec_blk" [arch/i386/crypto/aes.ko] undefined!
> [...]
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
> [3] Keywords:
> "make modules", "GREP_OPTIONS", "WARNING", "undefined"
>
> [X.] Suggestion to fix:
> Unset GREP_OPTIONS within make process.
While I admit that this will break the build, I think it's safe to say that
there are hundreds of environment variables that will influence the kbuild
system and makefiles. It's going to be an uphill battle if you want to fix each
and every occurrence of a *possible* build breakage due to an environment
variable being set wrongly.
I think it's perfectly fine for the kbuild system to expect a reasonably sane
and clean build system. Those who want to set specific variables to influence
their build should be able to do so as well, without getting settings removed.
In your case, I would suggest not setting this option by default in your shell ;)
Cheers,
Auke
next prev parent reply other threads:[~2007-05-17 4:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 3:26 PROBLEM: 2.6.21 - "make modules" with GREP_OPTIONS="-C1" (and other) Martin Christoph
2007-05-17 4:24 ` Kok, Auke [this message]
2007-05-17 7:11 ` 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=464BD915.7090209@foo-projects.org \
--to=sofar@foo-projects.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@da7a.de \
/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