From: Nick Clifton <nickc@redhat.com>
To: Danny Backx <danny.backx@scarlet.be>
Cc: binutils <binutils@sourceware.org>
Subject: Re: puzzled - old release works, newer doesn't
Date: Tue, 25 Apr 2006 17:39:00 -0000 [thread overview]
Message-ID: <444E5ABD.8070209@redhat.com> (raw)
In-Reply-To: <1144794175.3705.14.camel@dannypc>
Hi Danny,
> The old environment is based on gcc 3.4.2, gas 2.13.2, binutils 2.15.
> (Yes there's a mixup there.) The new environment is using gcc 4.1 and
> binutils 2.16. In all versions, the target platform is "arm-wince-pe".
>
> The person who created this distribution explains the mixup by saying
> that the GAS from 2.13 works, whereas the one in newer binutils doesn't.
>
> My personal experience with the 2.16 release appears to confirm that.
Are you upgrading to the new GCC new GAS and new LD all at the same time
? If not then that might be the cause.
Are you aware of the --support-old-code linker switch which is specific
to the arm-wince-pe target ? Using this might help you.
Using the latest binutils sources from CVS repository might also help.
If not then I would recommend comparing a disassembly of a working
binary and broken binary to see where there are changes. (Do not
compare the object files, but linked binaries. This should allow you to
find out how relocs may have been processed differently).
Cheers
Nick
next prev parent reply other threads:[~2006-04-25 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 23:06 Danny Backx
2006-04-25 17:39 ` Nick Clifton [this message]
2006-04-25 21:15 ` Pedro Alves
2006-04-27 2:23 ` Pedro Alves
2006-04-27 1:32 ` Danny Backx
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=444E5ABD.8070209@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=danny.backx@scarlet.be \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).