mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.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: Thu, 17 May 2007 09:11:36 +0200	[thread overview]
Message-ID: <20070517071136.GB3690@uranus.ravnborg.org> (raw)
In-Reply-To: <464BCB66.2090205@da7a.de>

On Thu, May 17, 2007 at 05:26:30AM +0200, 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.

Thanks for reporting this - I gues this took some time to
find the root cause of the problem.

Albeit fixing it seems simple I will consider it for a
while. In the kernel we use several tools like:
awk, grep, perl, ls, rm, mv, cmp etc and then
we should audit all of these to check if similar
things could occur.

If someone steps up to do the check (including
all the tools I missed) I would be very grateful.

	Sam

      parent reply	other threads:[~2007-05-17  7:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17  3:26 Martin Christoph
2007-05-17  4:24 ` Kok, Auke
2007-05-17  7:11 ` Sam Ravnborg [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=20070517071136.GB3690@uranus.ravnborg.org \
    --to=sam@ravnborg.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

all inboxes | Powered by JetHome®