lkml.org 
[lkml]   [2004]   [Oct]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFC] ARM binutils feature churn causing kernel problems
From
Date
On Tue, 2004-10-05 at 14:14, Russell King wrote:

> > Why don't you pass s to is_arm_mapping_symbol and have it do the same
> > thing as you've done in get_ksymbol?
>
> "sym_entry" is not an ELF symtab structure - it's a parsed version
> of the `nm' output, and as such does not contain the symbol type nor
> binding information.
>

Ah. That makes the question in your previous message make more sense
then. What options do you pass to nm?

Looking at the output of nm -fsysv shows that currently the mapping
symbols are being incorrectly typed (the EABI requires them to be
STT_NOTYPE, but the previous ELF specification -- not supported by GNU
utils -- required them to be typed by the data they addressed. I'll
submit a patch for that shortly).

> > ----------------------------------------------------------------
> > This e-mail message is intended for the addressee(s) only and may
> > contain information that is the property of, and/or subject to a
> > ...
> Does this apply to your message? It would appear that third parties
> subscribed to linux-kernel are not allowed to read your messages
> because they're not an "intended recipient" !

In this case no, which is why I reposted the message without it. It was
an oversight (I have to remove the boilerplate when I *don't* need it
rather than add it when I do).

R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

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