From: Adrian Bunk <bunk@fs.tum.de>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel makefiles broken?
Date: Wed, 2 Oct 2002 14:12:55 +0200 (CEST) [thread overview]
Message-ID: <Pine.NEB.4.44.0210021410150.10143-100000@mimas.fachschaften.tu-muenchen.de> (raw)
In-Reply-To: <20021002114028.C24770@flint.arm.linux.org.uk>
On Wed, 2 Oct 2002, Russell King wrote:
> Hi,
Hi Russell,
> I've noticed on two machines now that the kernel makefiles seem to have
> changed their behaviour. One x86 RH-based, and one parisc debian based.
>
> make seems to ignores errors from gcc, and only stops when trying to link.
> On a PARISC box, I've seen the build get all the way though to successfully
> linking vmlinux, even with compilation failures. Obviously not ideal,
> since vmlinux may not reflect reality.
>...
known bug, already fixed in Linus' BK tree, patch is below.
cu
Adrian
--- a/Rules.make Tue Oct 1 21:00:23 2002
+++ b/Rules.make Tue Oct 1 21:00:23 2002
@@ -517,13 +517,6 @@
include $(cmd_files)
endif
-# Emacs compile mode works best with relative paths to find files (OK
-# if verbose, as it tracks the make[1] entries and exits, etc.)
-
-ifneq ($(KBUILD_VERBOSE),1)
- filter-output = 2>&1 | sed 's \(^[^/][A-Za-z0-9_./-]*:[ 0-9]\) $(RELDIR)/\1 '
-endif
-
# function to only execute the passed command if necessary
if_changed = $(if $(strip $? \
@@ -543,7 +536,7 @@
$(filter-out $(cmd_$@),$(cmd_$(1)))),\
@set -e; \
$(if $($(quiet)cmd_$(1)),echo ' $($(quiet)cmd_$(1))';) \
- $(cmd_$(1)) $(filter-output); \
+ $(cmd_$(1)); \
$(TOPDIR)/scripts/fixdep $(depfile) $@ $(TOPDIR) '$(cmd_$(1))' > $(@D)/.$(@F).tmp; \
rm -f $(depfile); \
mv -f $(@D)/.$(@F).tmp $(@D)/.$(@F).cmd)
prev parent reply other threads:[~2002-10-02 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 10:40 kernel makefiles broken? Russell King
2002-10-02 12:10 ` Bruce Harada
2002-10-02 12:12 ` Adrian Bunk [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=Pine.NEB.4.44.0210021410150.10143-100000@mimas.fachschaften.tu-muenchen.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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).