From: Jun Sun <jsun@mvista.com>
To: linux-mips@linux-mips.org
Cc: jsun@mvista.com
Subject: [PATCH] halloween candy for make mips/mips64
Date: Thu, 31 Oct 2002 11:10:55 -0800 [thread overview]
Message-ID: <20021031111055.C6408@mvista.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 211 bytes --]
For lazy fingers, this patch saves quite some typing when
you work on mips64. It detects which arch you are working with
from .config if it is present. Otherwise, it defaults to
mips.
Like this treat?
Jun
[-- Attachment #2: junk --]
[-- Type: text/plain, Size: 432 bytes --]
diff -Nru Makefile.orig Makefile
--- Makefile.orig Wed Sep 11 05:44:23 2002
+++ Makefile Thu Oct 31 11:02:47 2002
@@ -5,7 +5,7 @@
KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)
-ARCH = mips
+ARCH = $(shell echo mips`grep '^CONFIG_MIPS64=y$$' .config | sed -e 's/..*/64/'`)
KERNELPATH=kernel-$(shell echo $(KERNELRELEASE) | sed -e "s/-//g")
CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
reply other threads:[~2002-10-31 19:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021031111055.C6408@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@linux-mips.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