From: zzs <zzs213@126.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] eldk5.0 generate illegal instruction for at91rm9200
Date: Sat, 16 Jul 2011 16:05:55 +0800 [thread overview]
Message-ID: <20110716080555.GA17211@greatfirst.com> (raw)
In-Reply-To: <20110715180002.053D017A322A@gemini.denx.de>
>
> Thanks again for the feedback. I have documented this issue in the
> ELDK FAQ section:
>
> http://www.denx.de/wiki/view/ELDK-5/QuestionsAndAnswers#GCC_generates_illegal_opcodes_fo
>
Yes. When using "USE_PRIVATE_LIBGCC=yes make my_board_name". It works
well. And the kernel works fine too because linux kernel has private libgcc
code too.
But when I examine the *.so files in eldk5.0, Almost all of them has
'clz' opcode. So if I use them in my aplication like busybox. It will
crash.
So I think the best way is to rebuild eldk5.0 for armv4. Did you tell
me how to configure eldk5.0 to build for armv4. And why eldk5.0 hasn't
a release for armv4, Is armv4 too old and has no value to support it?
--
Best Regards,
zzs
next prev parent reply other threads:[~2011-07-16 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 6:13 [U-Boot] at91rm9200 undef runtime error with eldk 5.0 zzs
2011-07-13 8:40 ` Wolfgang Denk
2011-07-13 10:46 ` zzs
2011-07-13 10:57 ` Wolfgang Denk
2011-07-13 11:20 ` zzs
2011-07-15 16:15 ` [U-Boot] eldk5.0 generate illegal instruction for at91rm9200 zzs
2011-07-15 17:22 ` Wolfgang Denk
2011-07-15 18:00 ` Wolfgang Denk
2011-07-16 8:05 ` zzs [this message]
2011-07-16 8:30 ` Andreas Bießmann
2011-07-16 8:33 ` Wolfgang Denk
2011-07-16 8:10 ` Albert ARIBAUD
2011-07-16 8:34 ` Wolfgang Denk
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=20110716080555.GA17211@greatfirst.com \
--to=zzs213@126.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.