All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Compiling with arm-eabi and YAFFS2
Date: Sat, 24 Oct 2009 13:31:22 -0500	[thread overview]
Message-ID: <4AE347FA.203@windriver.com> (raw)
In-Reply-To: <1256308142.2504.35.camel@cpilinux.cdsrail.com>

Chris Isbell wrote:
> U-Boot 2009.08 fails to compile with the arm-eabi compiler (V4.1.0 and
> V4.3.1) when YAFFS2 support is enabled (CONFIG_YAFFS2 defined as 1). It
> reports undefined symbols. (JFFS2 support compiles successfully.)
> 
> Having investigated, it appears that a work around is to create dummy
> functions as follows:
> 
> #ifdef CONFIG_YAFFS2
> /*
> * These stub functions are needed when using the arm-eabi compiler with
> YAFFS2 
> * support. This is a complete hack and will probably need to be revised.
> * (Chris Isbell 23rd October 2009.)
> */
> void abort(void)
> {
> 
> }
> 
> void __exidx_start(void)
> {
> 
> }
> 
> void __exidx_end(void)
> {
> 
> }
> #endif
> 
> For convenience, I included these temporarily with my board-specific
> initialisation code - which is clearly not a good place.
> 
> Has anyone else run into this problem and is there a more elegant
> solution?

Which board are you using ?
Can you supply the $(CROSS_COMPILE)-gcc -v ?

Thanks
Tom

> 
> Thanks,
> 
> 

  reply	other threads:[~2009-10-24 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23 14:29 [U-Boot] Compiling with arm-eabi and YAFFS2 Chris Isbell
2009-10-24 18:31 ` Tom [this message]
2009-10-26  7:42   ` Chris Isbell
2009-10-26  8:27     ` Jello huang
2009-10-26 12:41       ` Tom
2009-10-26 14:36         ` Chris Isbell

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=4AE347FA.203@windriver.com \
    --to=tom.rix@windriver.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.