linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: vger 2.2.10 compile failures
Date: Fri, 23 Jul 1999 14:53:09 +0200	[thread overview]
Message-ID: <19990723145309.026628@mail.mipsys.com> (raw)
In-Reply-To: <19990723144647.023789>


On Fri, Jul 23, 1999, Benjamin Herrenschmidt <bh40@calva.net> wrote:

>I'm getting link errors when compiling today's vger 2.2.10 with xmon support
>enabled:
>
>arch/ppc/xmon/x.o: In function `backtrace':
>arch/ppc/xmon/x.o(.text+0x129e): undefined reference to `ret_from_int'
>arch/ppc/xmon/x.o(.text+0x12a2): undefined reference to `ret_from_syscall_1'
>arch/ppc/xmon/x.o(.text+0x12a6): undefined reference to `ret_from_int'
>arch/ppc/xmon/x.o(.text+0x12aa): undefined reference to `ret_from_syscall_1'
>arch/ppc/xmon/x.o(.text+0x12ae): undefined reference to `ret_from_syscall_2'
>arch/ppc/xmon/x.o(.text+0x12b6): undefined reference to `ret_from_syscall_2'
>
>Apparently, the name of those symbols changed, I'll try to fix xmon here, but
>maybe someone already did it (Paul ?)

BTW. Here's the patch (it compiles, I beleive it works too but I didn't
test xmon yet):

diff -uNr linux.orig/arch/ppc/xmon/xmon.c linux/arch/ppc/xmon/xmon.c
--- linux.orig/arch/ppc/xmon/xmon.c     Thu Jul 22 22:12:16 1999
+++ linux/arch/ppc/xmon/xmon.c  Fri Jul 23 14:49:39 1999
@@ -472,7 +472,7 @@
        unsigned sp;
        unsigned stack[2];
        struct pt_regs regs;
-       extern char ret_from_int, ret_from_syscall_1, ret_from_syscall_2;
+       extern char int_return, syscall_ret_1, syscall_ret_2;
        extern char lost_irq_ret, do_bottom_half_ret, do_signal_ret;
 
        if (excp != NULL)
@@ -485,9 +485,9 @@
                if (mread(sp, stack, sizeof(stack)) != sizeof(stack))
                        break;
                printf("%x ", stack[1]);
-               if (stack[1] == (unsigned) &ret_from_int
-                   || stack[1] == (unsigned) &ret_from_syscall_1
-                   || stack[1] == (unsigned) &ret_from_syscall_2
+               if (stack[1] == (unsigned) &int_return
+                   || stack[1] == (unsigned) &syscall_ret_1
+                   || stack[1] == (unsigned) &syscall_ret_2
                    || stack[1] == (unsigned) &lost_irq_ret
                    || stack[1] == (unsigned) &do_bottom_half_ret
                    || stack[1] == (unsigned) &do_signal_ret) {


-- 
           Perso. e-mail: <mailto:bh40@calva.net>
           Work   e-mail: <mailto:benh@mipsys.com>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>




[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

       reply	other threads:[~1999-07-23 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19990723144647.023789>
1999-07-23 12:53 ` Benjamin Herrenschmidt [this message]
1999-07-23 12:46 vger 2.2.10 compile failures Benjamin Herrenschmidt
1999-07-24  1:14 ` Paul Mackerras

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=19990723145309.026628@mail.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.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).