linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] remove .tmp_gas_check
Date: Mon, 7 Feb 2005 09:23:56 +0100	[thread overview]
Message-ID: <20050207082356.GA29823@suse.de> (raw)
In-Reply-To: <20050206224306.GG7686@smtp.west.cox.net>

 On Sun, Feb 06, Tom Rini wrote:

> On Sun, Feb 06, 2005 at 10:56:00PM +0100, Olaf Hering wrote:
> >  On Sun, Feb 06, Tom Rini wrote:
> > 
> > > On Sun, Feb 06, 2005 at 10:15:06PM +0100, Olaf Hering wrote:
> > > 
> > > >  On Sun, Feb 06, Tom Rini wrote:
> > > > 
> > > > > I agree you shouldn't have to see it.  I'm saying the problem is the
> > > > > variable shouldn't be evaluated.
> > > > 
> > > > This patch seems to work for me.
> > > 
> > > What I don't like is that checkbin shouldn't be evaluated for 'tags' or
> > > other non-compile targets, so you don't need those explicit rm's.  Also,
> > > you forgot the signed-off-by line :)
> > 
> > Why should make tags or oldconfig ever care about the installed toolchain?
> 
> It shouldn't, and 'tags' at least shouldn't depend on 'checkbin'

tags does not call checkbin, so this part is ok.

> > How should the tmpfile disappear if one calls make checkbin with success?
> 
> On make clean, like the other .tmp files that are around at the end of a
> kernel compile (kallsyms/modules/maybe something else).

Thats ok now.

> > Maybe I misunderstood you.
> 
> I think so.  We both agree there should be no ppc-specific .tmp files
> around after certain make targets.  I'm saying that there's always some
> .tmp files generated on every arch for certain targets, and removed with
> a clean.  PPC should only create .tmp files (And leave them alone) in
> the cases where every arch generates some .tmp files.

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-07 09:21:25.941904406 +0100
@@ -112,26 +112,24 @@ 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 $$?)
 # 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)
 
 checkbin:
-ifeq ($(GCC_VERSION)$(BAD_GCC_AS),03041)
-	@echo -n '*** ${VERSION}.${PATCHLEVEL} kernels no longer build '
-	@echo 'correctly with gcc-3.4 and your version of binutils.'
-	@echo '*** Please upgrade your binutils or downgrade your gcc'
-	@false
-endif
-ifneq ($(AS_ALTIVEC),0)
-	echo $(AS_ALTIVEC)
-	@echo -n '*** ${VERSION}.${PATCHLEVEL} kernels no longer build '
-	@echo 'correctly with old versions of binutils.'
-	@echo '*** Please upgrade your binutils to 2.12.1 or newer'
-	@false
-endif
-	@true
+	@if test "$(GCC_VERSION)" = "0304" ; then \
+		if ! /bin/echo mftb 5 | $(AS) -v -mppc -many -o $(TOUT) >/dev/null 2>&1 ; then \
+			echo -n '*** ${VERSION}.${PATCHLEVEL} kernels no longer build '; \
+			echo 'correctly with gcc-3.4 and your version of binutils.'; \
+			echo '*** Please upgrade your binutils or downgrade your gcc'; \
+			false; \
+		fi ; \
+	fi
+	@if ! /bin/echo dssall | $(AS) -many -o $(TOUT) >/dev/null 2>&1 ; then \
+		echo -n '*** ${VERSION}.${PATCHLEVEL} kernels no longer build ' ; \
+		echo 'correctly with old versions of binutils.' ; \
+		echo '*** Please upgrade your binutils to 2.12.1 or newer' ; \
+		false ; \
+	fi
 
 CLEAN_FILES +=	include/asm-$(ARCH)/offsets.h \
 		arch/$(ARCH)/kernel/asm-offsets.s \

      reply	other threads:[~2005-02-07  8:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06 12:50 [PATCH] remove .tmp_gas_check Olaf Hering
2005-02-06 16:54 ` 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 [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=20050207082356.GA29823@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).