From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Takashi Oe <toe@unlserve.unl.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: ld bug?
Date: Fri, 15 Sep 2000 03:55:06 +0100 [thread overview]
Message-ID: <200009150254.DAA20954@hyperion.valhalla.net> (raw)
> c039c3e0 D int_control
>
> as opposed to c03ac3e0 used in vmlinux. So, it appears that ld or
This looks about the same as the difference reported by ksymoops (when it
refuses to work - reporting a mismatch between System.map and /proc/ksyms).
but I was seeing that on 2.2.17 (however, using the toolchain upgrades
recommended for 2.4.0).
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-09-15 2:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-15 2:55 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-15 13:09 ld bug? mikejc
2000-09-15 14:08 ` Takashi Oe
2000-09-13 19:32 zeroing pages in the idle task? Geert Uytterhoeven
2000-09-15 2:28 ` ld bug? Takashi Oe
2000-09-15 3:00 ` Kaoru Fukui
2000-09-15 3:16 ` Paul Mackerras
2000-09-15 3:44 ` Takashi Oe
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=200009150254.DAA20954@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toe@unlserve.unl.edu \
/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).