es.
>
>
> > Which source file should I put my stuff into ? An existing one, a new
> > one ?
>
> An existing one.
>
> Cheers
>Nick
Ok, patch attached.
Suggested ChangeLog entry in attachment "cl".
Danny
--
Danny Backx ; danny.backx
ink I need a source file that doesn't get the XX treatment
> > to put both functions in as non-static functions. But I am probably
> > overlooking something, I'm new to the binutils source.
>
> No, I think that you are right.
>
> Cheers
>Nick
>
>
--
On Fri, 2008-04-04 at 08:10 +0100, Nick Clifton wrote:
> > Didn't know about that. I've used it, and added one or more lines to 30
> > other .c files. In most cases this is just
> >
> > #define bfd_pe_print_pdata NULL
>
> Shouldn't that be:
>
>#define bfd_pe_print_pdata pe_print_data
>
> ie
ight for this because this function is not
to be treated with the XX replacement stuff. However, pe-arm-wince.c
doesn't seem right either because the pe_print_ce_compressed_pdata
function is to be used both for ARM and for SH.
So where should I put it (and its helper functions) ?
Thanks f
This has been on my todo-list for far too long, apologies.
I've tried to tackle the conditional compilation part, and would like
your renewed input on it, I may have missed some points. Naming for
instance.
Diffs in the attachment are relative to the cegcc svn, I've checked and
they patch cleanly
:
- a sample ChangeLog entry
- the patch in its current state
- a gzipped sample file on which this can be used to produce the output
as above. I've renamed it slightly, to avoid virus scanners.
Please advise on how to proceed.
Danny
--
Danny Backx ; danny.backx - at - scarlet.b
