From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel@lists.openembedded.org
Subject: Re: EABI pain and frustration!
Date: Fri, 05 Feb 2010 13:29:01 +0100 [thread overview]
Message-ID: <4B6C0F0D.8030308@vollmann.ch> (raw)
In-Reply-To: <1497161523.3479291265205781088.JavaMail.root@sz0154a.westchester.pa.mail.comcast.net>
On 02/03/10 15:03, pspreadborough@comcast.net wrote:
> My 2.6.29 kernel is built with the CodeSourcery arm-2009q3-67-arm-none-linux-gnueabi
> compiler and has the EABI and OABI_COMPAT config options enabled. Using this kernel
> I can boot my SA1110 iPaq into a OABI ramfs with no problems, however if I build a
> "HelloWorld" executable with the same compiler and try and run it I get an "Illegal Instruction"
> error. I build the test program using static linking, select the correct machine type and tune
> options but to no avail, I always get the illegal instruction.
Just checking: are you sure this is an EABI/OABI problem and not a
Thumb code problem?
Detlef
next prev parent reply other threads:[~2010-02-05 13:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 14:03 EABI pain and frustration! pspreadborough
2010-02-03 14:43 ` Koen Kooi
2010-02-03 15:59 ` Khem Raj
2010-02-05 12:29 ` Detlef Vollmann [this message]
2010-02-05 13:31 ` pspreadborough
2010-02-05 18:00 ` Khem Raj
2010-02-05 20:43 ` Travis Stratman
2010-02-05 21:41 ` Khem Raj
2010-02-05 22:53 ` Travis Stratman
2010-02-06 14:01 ` Phil Blundell
2010-02-06 16:24 ` pspreadborough
[not found] <1525882292.3655251265221536810.JavaMail.root@sz0154a.westchester.pa.mail.comcast.net>
2010-02-03 18:32 ` pspreadborough
2010-02-03 18:39 ` Koen Kooi
[not found] <1444973837.415081265420091001.JavaMail.root@sz0154a.westchester.pa.mail.comcast.net>
2010-02-06 1:37 ` pspreadborough
2010-02-06 16:27 ` Khem Raj
2010-02-06 16:38 ` pspreadborough
2010-02-06 17:27 ` Khem Raj
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=4B6C0F0D.8030308@vollmann.ch \
--to=dv@vollmann.ch \
--cc=openembedded-devel@lists.openembedded.org \
/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