[lkml]   [2004]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.8-rc2-mm1
On Sun, Aug 01, 2004 at 05:33:34AM -0700, William Lee Irwin III wrote:
> William Lee Irwin III <> wrote:
> >> There's trouble here with the link checking; it pukes all over
> >> sparc32's btfixup stuff. Not entirely sure what the proper form of a
> >> solution is.
> On Sun, Aug 01, 2004 at 01:05:32AM -0700, Andrew Morton wrote:
> > Do you mean the "check vmlinux for undefined symbols" thing?
> > That's proving to be a royal pain, although rmk's arguments for needing it
> > are good. Could you find a way of fixing it up?
> I may need core help. The executable is postprocessed by a program in
> arch/sparc/boot/ and so some kind of hook to give it a chance to
> properly fix up the symbol table (which I'll have to add afresh), for
> instance, an extra stage of .tmp_vmlinux*, seems to be needed.

Took a look at this and atm compiling a sparc tool-chain to try it out.
What about moving the check added by rmk to kallsyms.c?
This would remove the extra pass on vmlinux which is for no use for
most people anyway. On the other hand an error could go unpassed
because we (for now) do not do the kallsyms stuff if not configured in.

We could make the kallsyms run independent on the configuration, but
only link in the symbols if required to do so.
This would also allow us to have architecture specific final-linking
rules in one place if sparc needs special rules.
Today kallsyms already knows about 'SDA_BASE*_' only valid for ppc.

wli - can you post the output of a failing sparc compile?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:04    [W:0.062 / U:2.600 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site