linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>, linux-next@vger.kernel.org
Subject: Re: linux-next: sparc tree build failure
Date: Mon, 1 Dec 2008 06:41:40 +0100	[thread overview]
Message-ID: <20081201054140.GA21718@uranus.ravnborg.org> (raw)
In-Reply-To: <20081201104639.5080f12e.sfr@canb.auug.org.au>

On Mon, Dec 01, 2008 at 10:46:39AM +1100, Stephen Rothwell wrote:
> Hi Dave,
> 
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
> 
>   GEN     /scratch/sfr/powerpc_ppc64_defconfig/Makefile
> ***
> *** Can't find default configuration "arch/sparc/configs/ppc64_defconfig"!
> ***
> 
> Caused by commit 9cdcf85e1bf5dca97c1304292810041af2fcbd42 ("Subject:
> [PATCH 08/10] sparc,sparc64: unify Makefile") which seems to arbitrarily
> set SRCARCH in the top level make file to sparc!
Crap - missed an if/endif
Fix is simple:
diff --git a/Makefile b/Makefile
index 0043224..45f4300 100644
--- a/Makefile
+++ b/Makefile
@@ -206,7 +206,9 @@ ifeq ($(ARCH),x86_64)
 endif
 
 # Additional ARCH settings for sparc
+ifeq ($(ARCH),sparc64)
        SRCARCH := sparc
+endif
 
 # Where to locate arch specific headers
 hdr-arch  := $(SRCARCH)

> 
> (One way to take over the world, I guess :-))
Reminds me about Pinky & Brain - we almost suceeded!

	Sam

  reply	other threads:[~2008-12-01  5:40 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-30 23:46 linux-next: sparc tree build failure Stephen Rothwell
2008-12-01  5:41 ` Sam Ravnborg [this message]
2008-12-01  7:23   ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2009-11-26  9:16 Stephen Rothwell
2009-11-26 23:28 ` David Miller
2009-11-27  9:00   ` Thomas Gleixner
2009-11-06  7:02 Stephen Rothwell
2009-11-06  8:19 ` David Miller
2009-11-06  8:26   ` David Miller
2009-11-06  8:27     ` David Miller
2009-11-07  2:35     ` Stephen Rothwell
2009-11-05  7:50 Stephen Rothwell
2009-11-05  7:53 ` David Miller
2009-11-05  8:00   ` David Miller
2009-11-05 14:44     ` Kristoffer Glembo
2009-11-13 10:34     ` Kristoffer Glembo
2009-11-13 14:57       ` David Miller
2009-10-05  7:43 Stephen Rothwell
2009-10-05  7:45 ` David Miller
2009-04-09  5:17 Stephen Rothwell
2009-04-09  5:27 ` Ingo Molnar
2009-04-09  5:28   ` David Miller
2009-04-09  5:36     ` Ingo Molnar
2009-04-09  5:40       ` David Miller
2009-04-09  5:53         ` Ingo Molnar
2009-04-09  5:59           ` David Miller
2009-04-09  5:28 ` David Miller
2009-04-14  3:45 ` Stephen Rothwell
2008-12-04  8:54 Stephen Rothwell
2008-12-04 11:47 ` Sam Ravnborg
2008-12-02  6:24 Stephen Rothwell
2008-12-02 11:22 ` Rusty Russell
2008-12-04  0:04   ` David Miller
2008-07-28  6:38 Stephen Rothwell
2008-07-28  8:21 ` Sam Ravnborg
2008-07-28  9:31   ` Adrian Bunk
2008-07-28 15:12     ` Stephen Rothwell
2008-07-28 10:12   ` Stephen Rothwell
2008-07-28 11:16     ` Sam Ravnborg
2008-07-25  7:05 Stephen Rothwell
2008-07-25  7:09 ` Stephen Rothwell
2008-07-26  9:25 ` David Miller
2008-08-04  4:26 ` David Miller
2008-08-04  5:35   ` Stephen Rothwell
2008-07-22  7:41 Stephen Rothwell
2008-07-22 22:47 ` David Miller

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=20081201054140.GA21718@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=davem@davemloft.net \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).