From: Paul Mackerras <paulus@cs.anu.edu.au>
To: bh40@calva.net
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: vger 2.2.10 compile failures
Date: Sat, 24 Jul 1999 11:14:01 +1000 [thread overview]
Message-ID: <199907240114.LAA01151@tango.anu.edu.au> (raw)
In-Reply-To: <19990723144647.023789@mail.mipsys.com> (message from Benjamin Herrenschmidt on Fri, 23 Jul 1999 14:46:47 +0200)
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'
I got tricked by cvs about this, maybe you have too. I had a stable
(linux_2_2) cvs tree, and when I did `cvs update -dP', I got an xmon
directory, but it was the xmon from the head of the tree, i.e. the
devel branch. I should have been doing `cvs update -dP -rlinux_2_2',
of course. If you do that it should give you the xmon from the stable
branch (which didn't actually exist until yesterday, but now has the
xmon.c with the correct contents).
Paul.
[[ 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. ]]
next prev parent reply other threads:[~1999-07-24 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-23 12:46 vger 2.2.10 compile failures Benjamin Herrenschmidt
1999-07-24 1:14 ` Paul Mackerras [this message]
[not found] <19990723144647.023789>
1999-07-23 12:53 ` Benjamin Herrenschmidt
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=199907240114.LAA01151@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=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).