From: Olaf Hering <olh@suse.de>
To: Tom Rini <trini@kernel.crashing.org>, linuxppc-dev@ozlabs.org
Subject: [PATCH] remove .tmp_gas_check
Date: Sun, 6 Feb 2005 13:50:56 +0100 [thread overview]
Message-ID: <20050206125056.GA6394@suse.de> (raw)
make ARCH=ppc tags leaves a .tmp_gas_check file behind.
Just remove it after the as test.
Signed-off-by: Olaf Hering <olh@suse.de>
diff -purNx tags ../linux-2.6.11-rc3.orig/arch/ppc/Makefile ./arch/ppc/Makefile
--- ../linux-2.6.11-rc3.orig/arch/ppc/Makefile 2005-02-03 02:57:05.000000000 +0100
+++ ./arch/ppc/Makefile 2005-02-06 10:51:21.000000000 +0100
@@ -112,10 +112,10 @@ include/asm-$(ARCH)/offsets.h: arch/$(AR
TOUT := .tmp_gas_check
# Ensure this is binutils 2.12.1 (or 2.12.90.0.7) or later for altivec
# instructions.
-AS_ALTIVEC := $(shell echo dssall | $(AS) -many -o $(TOUT) >/dev/null 2>&1 ; echo $$?)
+AS_ALTIVEC := $(shell echo dssall | $(AS) -many -o $(TOUT) >/dev/null 2>&1 ; echo $$? ; rm -f $(TOUT))
# gcc-3.4 and binutils-2.14 are a fatal combination.
GCC_VERSION := $(call cc-version)
-BAD_GCC_AS := $(shell echo mftb 5 | $(AS) -mppc -many -o $(TOUT) >/dev/null 2>&1 && echo 0 || echo 1)
+BAD_GCC_AS := $(shell echo mftb 5 | $(AS) -mppc -many -o $(TOUT) >/dev/null 2>&1 ; echo $$? ; rm -f $(TOUT))
checkbin:
ifeq ($(GCC_VERSION)$(BAD_GCC_AS),03041)
next reply other threads:[~2005-02-06 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 12:50 Olaf Hering [this message]
2005-02-06 16:54 ` [PATCH] remove .tmp_gas_check Tom Rini
2005-02-06 16:56 ` Olaf Hering
2005-02-06 17:24 ` Tom Rini
2005-02-06 17:25 ` Olaf Hering
2005-02-06 20:04 ` Tom Rini
2005-02-06 20:08 ` Olaf Hering
2005-02-06 20:21 ` Tom Rini
2005-02-06 21:15 ` Olaf Hering
2005-02-06 21:49 ` Tom Rini
2005-02-06 21:56 ` Olaf Hering
2005-02-06 22:43 ` Tom Rini
2005-02-07 8:23 ` Olaf Hering
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=20050206125056.GA6394@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).