public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Miller <davem@davemloft•net>
Cc: linux-next@vger•kernel.org, Sam Ravnborg <sam@ravnborg•org>
Subject: linux-next: sparc tree build failure
Date: Tue, 22 Jul 2008 17:41:51 +1000	[thread overview]
Message-ID: <20080722174151.8dc8f29e.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

Hi Dave,

Today's (and for a few days) linux-next build (sparc32 defconfig) failed
like this:

In file included from include2/asm/page.h:4,
                 from arch/sparc/kernel/vmlinux.lds.S:4:
include/asm-sparc/page_64.h:11:2: #error No page size specified in kernel configuration

Due to the merge of page.h (I suspect).  The patch below fixes it.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

>From 2c8b8ccd3bb14cf6100ba86411d7ef676cf974df Mon Sep 17 00:00:00 2001
From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Tue, 22 Jul 2008 17:34:27 +1000
Subject: [PATCH] sparc32: pass -m32 when building vmlinux.lds

Otherwise it breaks since we merged asm/page.h

Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
 arch/sparc/Makefile |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/arch/sparc/Makefile b/arch/sparc/Makefile
index fef28e2..6668e60 100644
--- a/arch/sparc/Makefile
+++ b/arch/sparc/Makefile
@@ -18,6 +18,7 @@ CHECKFLAGS	+= -D__sparc__
 #KBUILD_CFLAGS += -g -pipe -fcall-used-g5 -fcall-used-g7
 KBUILD_CFLAGS += -m32 -pipe -mno-fpu -fcall-used-g5 -fcall-used-g7
 KBUILD_AFLAGS += -m32
+CPPFLAGS_vmlinux.lds += -m32
 
 #LDFLAGS_vmlinux = -N -Ttext 0xf0004000
 #  Since 2.5.40, the first stage is left not btfix-ed.
-- 
1.5.6.3


[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2008-07-22  7:42 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22  7:41 Stephen Rothwell [this message]
2008-07-22 22:47 ` linux-next: sparc tree build failure David Miller
  -- strict thread matches above, loose matches on Subject: below --
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-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-11-30 23:46 Stephen Rothwell
2008-12-01  5:41 ` Sam Ravnborg
2008-12-01  7:23   ` David Miller
2008-12-02  6:24 Stephen Rothwell
2008-12-02 11:22 ` Rusty Russell
2008-12-04  0:04   ` David Miller
2008-12-04  8:54 Stephen Rothwell
2008-12-04 11:47 ` Sam Ravnborg
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
2009-10-05  7:43 Stephen Rothwell
2009-10-05  7:45 ` David Miller
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-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-26  9:16 Stephen Rothwell
2009-11-26 23:28 ` David Miller
2009-11-27  9:00   ` Thomas Gleixner

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=20080722174151.8dc8f29e.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sam@ravnborg$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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