From: "Frank Ch. Eigler" <fche@redhat.com>
To: ?? ?? <dam_wang@hotmail.com>
Cc: sid@sources.redhat.com
Subject: Re: SID execution error
Date: Sat, 16 Nov 2002 15:29:00 -0000 [thread overview]
Message-ID: <20021116232922.GA27805@redhat.com> (raw)
In-Reply-To: <F1052hFOWd8T408Oh1p00000694@hotmail.com>
Hi -
> I built SID and a arm-target cross-toolchain and wanted to try sid, but I
> got some problem.
>
> The toolchain on my systerm was a prebuilt one, I download it from:
> http://www.lart.tudelft.nl/lartware/compile-tools/
> [...]
> then I compiled it with arm-linux-gcc:
> arm-linux-gcc -o test.exe test.c
The problem is that this toolchain probably produces arm-linux type
executables. While they may be ELF format files, they likely assume
a memory layout (and importantly, system libraries and system call ABI)
that is different from that of basic embedded ARM systems.
It's not hopeless to try to configure sid to try to emulate an arm-linux
environment. It'd be easier to get a plain embedded arm-elf toolchain,
or use the arm-linux one somehow without the linux target dependencies.
- FChE
next prev parent reply other threads:[~2002-11-16 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 5:50 汪 翼
2002-11-16 15:29 ` Frank Ch. Eigler [this message]
2002-11-16 22:01 汪 翼
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=20021116232922.GA27805@redhat.com \
--to=fche@redhat.com \
--cc=dam_wang@hotmail.com \
--cc=sid@sources.redhat.com \
/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).