From: Rusty Russell <rusty@rustcorp.com.au>
To: Keith Owens <kaos@sgi.com>
Cc: Joseph Fannin <jhf@rivenstone.net>, Andrew Morton <akpm@osdl.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
benh@kernel.crashing.org
Subject: Re: 2.6.7-mm6 - ppc32 inconsistent kallsyms data
Date: Tue, 06 Jul 2004 19:09:23 +1000 [thread overview]
Message-ID: <1089104963.9417.4.camel@bach> (raw)
In-Reply-To: <13859.1089099082@kao2.melbourne.sgi.com>
On Tue, 2004-07-06 at 17:31, Keith Owens wrote:
> This is a real linker problem on ppc32. The linker automatically adds
> _SDA_BASE_ and _SDA2_BASE_ symbols, these symbols are not defined in
> vmlinux.lds.S.
What type are those symbols? I'm surprised they're not 'A' which is
already ignored...
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
next prev parent reply other threads:[~2004-07-06 9:09 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 9:31 2.6.7-mm6 Andrew Morton
2004-07-05 10:18 ` 2.6.7-mm6 Christoph Hellwig
2004-07-05 10:44 ` 2.6.7-mm6 Christoph Hellwig
2004-07-05 10:32 ` 2.6.7-mm6 Redeeman
2004-07-05 13:54 ` 2.6.7-mm6 Frieder Buerzele
2004-07-05 14:41 ` 2.6.7-mm6 Redeeman
2004-07-05 10:39 ` 2.6.7-mm6 Martin Zwickel
2004-07-05 19:04 ` 2.6.7-mm6 Jurgen Kramer
2004-07-05 20:38 ` 2.6.7-mm6 - ppc32 inconsistent kallsyms data Joseph Fannin
2004-07-05 20:54 ` Andrew Morton
2004-07-06 2:06 ` Keith Owens
2004-07-06 7:31 ` Keith Owens
2004-07-06 7:43 ` Keith Owens
2004-07-06 20:54 ` Joseph Fannin
2004-07-06 9:09 ` Rusty Russell [this message]
2004-07-06 12:28 ` Keith Owens
2004-07-05 22:52 ` 2.6.7-mm6: ALSA: vortex_asXtalkGainsAllChan multiple definitions Adrian Bunk
2004-07-05 22:56 ` [patch] 2.6.7-mm6: let CDROM_PKTCDVD depend on experimental Adrian Bunk
2004-07-06 6:49 ` USB Lockups with 2.6.7-mm6, was Re: 2.6.7-mm6 Ralf Hildebrandt
2004-07-06 12:54 ` 2.6.7-mm6 William Lee Irwin III
2004-07-06 17:51 ` 2.6.7-mm6 Dmitry Torokhov
2004-07-06 18:55 ` 2.6.7-mm6 Jan-Benedict Glaw
2004-07-06 23:12 ` 2.6.7-mm6 William Lee Irwin III
2004-07-06 23:55 ` 2.6.7-mm6 William Lee Irwin III
2004-07-07 5:15 ` 2.6.7-mm6 Dmitry Torokhov
2004-07-07 6:37 ` 2.6.7-mm6 William Lee Irwin III
2004-07-07 12:47 ` 2.6.7-mm6 Dmitry Torokhov
2004-07-07 12:55 ` 2.6.7-mm6 William Lee Irwin III
2004-07-07 16:31 ` 2.6.7-mm6 Vojtech Pavlik
2004-07-07 17:15 ` 2.6.7-mm6 Dmitry Torokhov
2004-07-07 19:05 ` 2.6.7-mm6 Vojtech Pavlik
2004-07-06 22:34 ` 2.6.7-mm6 Andrew Morton
2004-07-06 22:45 ` 2.6.7-mm6 David S. Miller
2004-07-06 22:52 ` 2.6.7-mm6 William Lee Irwin III
2004-07-06 23:07 ` 2.6.7-mm6 Russell King
2004-07-06 23:36 ` 2.6.7-mm6 William Lee Irwin III
2004-07-07 0:02 ` 2.6.7-mm6 David S. Miller
2004-07-07 2:29 ` 2.6.7-mm6 Nick Piggin
2004-07-07 7:35 ` 2.6.7-mm6 Ingo Molnar
2004-07-07 21:02 ` 2.6.7-mm6 David S. Miller
2004-07-09 2:45 ` 2.6.7-mm6 Nick Piggin
2004-07-09 2:51 ` 2.6.7-mm6 William Lee Irwin III
2004-07-09 5:09 ` 2.6.7-mm6 Nick Piggin
2004-07-09 6:29 ` 2.6.7-mm6 Ingo Molnar
2004-07-09 6:58 ` 2.6.7-mm6 William Lee Irwin III
2004-07-09 7:07 ` 2.6.7-mm6 Nick Piggin
2004-07-09 7:16 ` 2.6.7-mm6 William Lee Irwin III
2004-07-06 14:49 ` 2.6.7-mm6 - USB problems Jesse Stockall
2004-07-07 16:44 ` 2.6.7-mm6 Jesse Barnes
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=1089104963.9417.4.camel@bach \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=jhf@rivenstone.net \
--cc=kaos@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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