mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@intercode.com.au>
To: sparclinux@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.5.54-sparc64 compile errors
Date: Sat, 4 Jan 2003 01:08:59 +1100 (EST)	[thread overview]
Message-ID: <Mutt.LNX.4.44.0301040101070.17638-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <Pine.LNX.3.96.1030102191604.22760J-100000@ligur.expressz.com>

On Thu, 2 Jan 2003, BODA Karoly jr. wrote:

> o And an error which with I can't do anything... :(
> 
>   sparc64-linux-gcc -Wp,-MD,arch/sparc64/kernel/.head.o.d -D__ASSEMBLY__
> -D__KERNEL__ -Iinclude -m64 -mcpu=ultrasparc -Wa,--undeclared-regs
> -nostdinc -iwithprefix include  -ansi  -c -o arch/sparc64/kernel/head.o
> arch/sparc64/kernel/head.S
> In file included from include/linux/cache.h:4,
>                  from include/asm/smp.h:11,
>                  from arch/sparc64/kernel/entry.S:15,
>                  from arch/sparc64/kernel/head.S:734:
> include/linux/kernel.h:31: warning: `ALIGN' redefined
> include/linux/linkage.h:24: warning: this is the location of the previous definition
> 

This is a namespace collision introduced with ALIGN() being moved to
kernel.h.  A patch below resolves this for sparc64 by not including some
non-asm headers when compiling assembler, although the namespace issue
itself may still need to be fixed (e.g. change ALIGN() to ALIGN_TO() 
in kernel.h ?).  

It looks like sparc32 has a similar problem.


- James
-- 
James Morris
<jmorris@intercode.com.au>

diff -urN -X dontdiff linux-2.5.54.orig/include/asm-sparc64/smp.h linux-2.5.54.w1/include/asm-sparc64/smp.h
--- linux-2.5.54.orig/include/asm-sparc64/smp.h	Wed Oct  9 22:39:39 2002
+++ linux-2.5.54.w1/include/asm-sparc64/smp.h	Sat Jan  4 00:43:28 2003
@@ -7,13 +7,14 @@
 #define _SPARC64_SMP_H
 
 #include <linux/config.h>
-#include <linux/threads.h>
-#include <linux/cache.h>
 #include <asm/asi.h>
 #include <asm/starfire.h>
 #include <asm/spitfire.h>
 
 #ifndef __ASSEMBLY__
+#include <linux/threads.h>
+#include <linux/cache.h>
+
 /* PROM provided per-processor information we need
  * to start them all up.
  */


  parent reply	other threads:[~2003-01-03 14:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 18:50 BODA Karoly jr.
2003-01-02 19:32 ` Sam Ravnborg
2003-01-03 14:08 ` James Morris [this message]
2003-01-03 15:34   ` BODA Karoly jr.
2003-01-03 16:36     ` James Morris
2003-01-03 18:55       ` BODA Karoly jr.
2003-01-04  0:28         ` James Morris
2003-01-06 14:59           ` BODA Karoly jr.
2003-01-04  2:14       ` David S. 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=Mutt.LNX.4.44.0301040101070.17638-100000@blackbird.intercode.com.au \
    --to=jmorris@intercode.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.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

all inboxes | Powered by JetHome®