From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tom <Tom.Rix@windriver.com>
Date: Sat, 24 Oct 2009 13:31:22 -0500
Subject: [U-Boot] Compiling with arm-eabi and YAFFS2
In-Reply-To: <1256308142.2504.35.camel@cpilinux.cdsrail.com>
References: <1256308142.2504.35.camel@cpilinux.cdsrail.com>
Message-ID: <4AE347FA.203@windriver.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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,
> 
>