From: Richard Earnshaw <rearnsha@arm.com>
To: mnshukla <mnshukla@cirrus.stpp.soft.net>
Cc: gcc@gcc.gnu.org, Richard.Earnshaw@arm.com
Subject: Re: Query
Date: Mon, 22 Jan 2001 06:27:00 -0000 [thread overview]
Message-ID: <200101221426.OAA03007@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: <3A6C412B.529B4827@cirrus.stpp.soft.net>
> Hi,
>
> I am using gcc for ArmLinux obtained from following site:
> arm-linux-cross.tar.bz2 from
> http://www.lart.tudelft.nl/lartware/compile-tools/ (LARTware Compiler
> tools)
>
> I cross compiled Linux and the OS (Linux) is working fine. Now, I am
> cross compiling an Application with for ARM-SDT compiler and generating
> an image in elf format and when I run it on ARM board (with Linux OS),
> it gives memory violation -- this may be because of non static linking
> (as there is no linker option in ARM-SDT for static linking). So I tried
> to cross-compile the applicatin and I wanted to link it by gcc - linker
> but I am not able to do it. This is because ARM-SDT generate object file
> in AOF format.
>
> Is there any utility to convert object files in AOF format to ELF
> format??
I'm not aware of any. The latest ARM SDT tools (well, ADS anyway)
generate ELF images. There are tools which convert from ELF to AOF, but
not vice versa.
next prev parent reply other threads:[~2001-01-22 6:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 6:20 Query MNShukla
2001-01-22 6:27 ` Richard Earnshaw [this message]
2001-01-22 12:28 ` Query Philip Blundell
2001-04-19 3:29 Query MNShukla
2001-04-19 5:51 ` Query Nick Clifton
2001-04-19 21:54 ` Query MNShukla
2001-04-20 3:29 ` Query Philip Blundell
2001-04-19 9:47 ` Query Toshi Morita
2001-12-06 1:37 Query Bansal, Shashank
2001-12-06 1:45 ` Query Bansal, Shashank
2001-12-06 5:19 ` Query Jack Lloyd
2001-12-06 7:44 ` Query Tim Prince
2002-03-01 21:14 query sunil suhas petwe
2002-03-10 4:44 ` query Andrea 'Fyre Wyzard' Bocci
2003-04-24 11:48 Query Vijay Kamath
2003-04-24 12:25 ` Query Andrew Haley
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=200101221426.OAA03007@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc@gcc.gnu.org \
--cc=mnshukla@cirrus.stpp.soft.net \
/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).