This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Fri Mar 29 10:21:05 2024 Envelope-to: j@jasper.es Delivery-date: Wed, 30 Oct 2013 17:15:40 +0100 Received: from localhost ([127.0.0.1] helo=squeeze.vs19.net) by squeeze.vs19.net with esmtp (Exim 4.80) (envelope-from ) id 1VbYQm-0007YD-H2 for j@jasper.es; Wed, 30 Oct 2013 17:15:40 +0100 Original-Recipient: rfc822;jasper@telfort.nl Received: from pop3.telfort.nl [213.75.3.52] by squeeze.vs19.net with POP3 (fetchmail-6.3.21) for (single-drop); Wed, 30 Oct 2013 17:15:40 +0100 (CET) Received: from cpxmta-msg04.kpnxchange.com (10.94.114.25) by cpxmbs-msg01.support.local (8.6.060.31) id 525DCADF00CA36A1 for jasper@telfort.nl; Wed, 30 Oct 2013 17:06:50 +0100 Received: from cpsmtpb-ews09.kpnxchange.com (213.75.39.14) by cpxmta-msg04.kpnxchange.com (8.6.060.14) id 522FB3D405C25D67 for jasper@telfort.nl; Wed, 30 Oct 2013 17:06:50 +0100 Received: from cpsps-ews02.kpnxchange.com ([10.94.84.169]) by cpsmtpb-ews09.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Wed, 30 Oct 2013 17:06:50 +0100 Received: from vger.kernel.org ([209.132.180.67]) by cpsps-ews02.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Wed, 30 Oct 2013 17:06:50 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752603Ab3J3QGp (ORCPT ); Wed, 30 Oct 2013 12:06:45 -0400 Received: from mail.skyhub.de ([78.46.96.112]:39044 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751371Ab3J3QGo convert rfc822-to-8bit (ORCPT ); Wed, 30 Oct 2013 12:06:44 -0400 X-Virus-Scanned: Nedap ESD1 at mail.skyhub.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alien8.de; s=alien8; t=1383149202; bh=kMjCCoVQnXO5qgrQ2f8YaBumbXuMQcTCffWkVO57l14=; h=Date:From:To:Cc:Subject:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding; b=BZCS/YQ8K/teicWN3DehxUvJLgqBNgfVBoWwe Received: from mail.skyhub.de ([127.0.0.1]) by localhost (door.skyhub.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Hmm1htJs6ls8; Wed, 30 Oct 2013 17:06:41 +0100 (CET) Received: from liondog.tnic (p54B7EB73.dip0.t-ipconnect.de [84.183.235.115]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 99C151DA255; Wed, 30 Oct 20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alien8.de; s=alien8; t=1383149201; bh=kMjCCoVQnXO5qgrQ2f8YaBumbXuMQcTCffWkVO57l14=; h=Date:From:To:Cc:Subject:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding; b=HR1pHtrr4gQJB3M8JanSvAPijfLxlIHWodFXE Received: by liondog.tnic (Postfix, from userid 1000) id CF923102469; Wed, 30 Oct 2013 17:06:35 +0100 (CET) Date: Wed, 30 Oct 2013 17:06:35 +0100 From: Borislav Petkov To: linux-kbuild@vger.kernel.org, lkml Cc: x86-ml Subject: Kbuild: Ignore GREP_OPTIONS env variable Message-Id: <20131030160635.GE13290@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8BIT User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-Id: X-Mailing-List: linux-kernel@vger.kernel.org X-OriginalArrivalTime: 30 Oct 2013 16:06:50.0889 (UTC) FILETIME=[0B1BAF90:01CED58A] X-RcptDomain: telfort.nl Hi, this is just a general poll of what people think about the issue here, just so that at least we've talked about it. So I had defined GREP_OPTIONS=--color=always on one of my boxes and had forgotten about it and the kernel build started failing because we use grep quite a while in the tree and it started issuing shell color markup which generated garbage files, like the syscall headers on x86, for example. I have a fix below which seems to take care of it but what is the general opinion: Do we want to be more robust against the environment we find on a machine before building the kernel or let the user figure it out himself that he should be using GREP_OPTIONS=--color=auto in the first place and it is his own moronic fault if he does 'always'? Opinions, comments? Thanks. -- From: Borislav Petkov Subject: [PATCH] Kbuild: Ignore GREP_OPTIONS env variable MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit When building the kernel in a shell which defines GREP_OPTIONS so that grep behavior is modified, we can break the generation of the syscalls table like so: __SYSCALL_COMMON(0, sys_read, sys_read) __SYSCALL_COMMON(1, sys_write, sys_write) __SYSCALL_COMMON(10, sys_mprotect, sys_mprotect) ... This is just the initial breakage, later we barf when generating modules. In this case, GREP_OPTIONS contains "--color=always" which adds the shell colors markup and completely fudges the headers under ...generated/asm/. Fix that by ignoring the GREP_OPTIONS variable for the whole kernel build as we tend to use grep at a bunch of places. Signed-off-by: Borislav Petkov --- Makefile | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Makefile b/Makefile index 868c0eb67b08..7a2acd9a5d1c 100644 --- a/Makefile +++ b/Makefile @@ -16,6 +16,9 @@ NAME = One Giant Leap for Frogkind # o print "Entering directory ..."; MAKEFLAGS += -rR --no-print-directory +GREP_OPTIONS= +export GREP_OPTIONS + # Avoid funny character set dependencies unexport LC_ALL LC_COLLATE=C -- 1.8.4 -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/