From: Brian S. Park <brian.park@corelis.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] How to debug u-boot?
Date: Thu, 05 Jun 2008 19:13:55 -0700 [thread overview]
Message-ID: <200806060213.m562DaPR002810@mail.corelis.com> (raw)
Hi every one.
I need help with debugging u-boot. If I comple u-Boot without -Os
optimization, I get bunch of errors about missing functions. They are
inline functions (in_be32, out_be32, out_8, etc) and I'm not sure how
to make sure they are included when building the code without optimization.
I'm using ELDK4.1 for windows and u-Boot-1.3.3
Any help or pointers will be appreciated.
Thanks
Brian
===============================================================
Brian S. Park brian.park at corelis.com (562) 926-6727 x132
---------------------------------------------------------------
Everything we do helps our customers get to market
FASTER with HIGHER quality and LOWER cost
===============================================================
next reply other threads:[~2008-06-06 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 2:13 Brian S. Park [this message]
2008-06-06 6:07 ` [U-Boot-Users] How to debug u-boot? Alessandro Rubini
2008-06-06 16:34 ` Brian S. Park
2008-06-09 9:53 ` Detlev Zundel
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 4:33 huasee
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=200806060213.m562DaPR002810@mail.corelis.com \
--to=brian.park@corelis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox