From: Jim Gifford <maillist@jg555.com>
To: sparclinux@vger.kernel.org
Subject: Re: Build Issue - Sparc64
Date: Thu, 12 Jan 2006 21:32:13 +0000 [thread overview]
Message-ID: <43C6CADD.30602@jg555.com> (raw)
In-Reply-To: <43C6A8A3.9090100@jg555.com>
Jim Gifford wrote:
> Anyone got any ideas. This is from the 2.6.15 build. We are doing some
> testing building a 64 bit kernel with no 32 bit support for testing
> purposes and we ran into this error. GCC 4, Binutils 2.16.1, Glibc 2.3.6.
>
> cc1: warnings being treated as errors
> arch/sparc64/kernel/process.c: In function 'show_regwindow32':
> arch/sparc64/kernel/process.c:174: warning: implicit declaration of
> function 'compat_ptr'
> arch/sparc64/kernel/process.c:174: warning: assignment makes pointer
> from integer without a cast
> make[1]: *** [arch/sparc64/kernel/process.o] Error 1
> make: *** [arch/sparc64/kernel] Error 2
>
Fixed the issue with this patch.
--- process.c.orig 2006-01-12 13:27:03.000000000 -0800
+++ process.c 2006-01-12 13:28:21.000000000 -0800
@@ -164,6 +164,7 @@
panic("Reboot failed!");
}
+#ifdef CONFIG_COMPAT
static void show_regwindow32(struct pt_regs *regs)
{
struct reg_window32 __user *rw;
@@ -189,6 +190,7 @@
r_w.ins[0], r_w.ins[1], r_w.ins[2], r_w.ins[3],
r_w.ins[4], r_w.ins[5], r_w.ins[6], r_w.ins[7]);
}
+#endif
static void show_regwindow(struct pt_regs *regs)
{
@@ -214,7 +216,11 @@
set_fs (old_fs);
}
} else {
- show_regwindow32(regs);
+ #ifdef CONFIG_COMPAT
+ show_regwindow32(regs);
+ #else
+ show_regwindow(regs);
+ #endif
return;
}
printk("l0: %016lx l1: %016lx l2: %016lx l3: %016lx\n",
--
----
Jim Gifford
maillist@jg555.com
next prev parent reply other threads:[~2006-01-12 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 19:06 Build Issue - Sparc64 Jim Gifford
2006-01-12 21:30 ` Jim Gifford
2006-01-12 21:32 ` Jim Gifford [this message]
2006-01-18 22:58 ` David S. Miller
2006-01-18 23:02 ` Jim Gifford
2006-01-18 23:04 ` David S. Miller
2006-01-19 0:32 ` Jim Gifford
2006-01-19 0:38 ` 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=43C6CADD.30602@jg555.com \
--to=maillist@jg555.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.