From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Compiling with arm-eabi and YAFFS2
Date: Mon, 26 Oct 2009 07:41:01 -0500 [thread overview]
Message-ID: <4AE598DD.3050107@windriver.com> (raw)
In-Reply-To: <88a4839a0910260127r319b507ds9e13d8fd6c613ead@mail.gmail.com>
In my android work. I use a separate compiler for the u-boot and
kernel, the Code Sourcery arm lite edition.
http://www.codesourcery.com/sgpp/editions.html#lite
Please try this.
Tom
Jello huang wrote:
> if u use eabi compiler to compile u-boot,there r some error.
> why not use abi compiler for u-boot.it can compile successful
>
> 2009/10/26 Chris Isbell <chris.isbell@cdsrail.com>
>
>> On Sat, 2009-10-24 at 13:31 -0500, Tom wrote:
>>> 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,
>>>>
>>>>
>> Tom,
>>
>> Board is Ronetix PM9263.
>>
>> The gcc version is reported as:
>>
>> Using built-in specs.
>> Target: arm-eabi
>> Configured
>> with: /home/jingyu/projects/gcc/android-toolchain/gcc-4.4.0/configure
>> --prefix=/usr/local --target=arm-eabi --host=i686-pc-linux-gnu
>> --build=i686-pc-linux-gnu --enable-languages=c,c++
>> --with-gmp=/home/jingyu/projects/gcc/toolchain_build/obj/temp-install
>> --with-mpfr=/home/jingyu/projects/gcc/toolchain_build/obj/temp-install
>> --disable-libssp --enable-threads --disable-nls --disable-libmudflap
>> --disable-libgomp --disable-libstdc__-v3 --disable-sjlj-exceptions
>> --disable-shared --with-float=soft --with-fpu=vfp --with-arch=armv5te
>> --enable-target-optspace --with-abi=aapcs --with-gcc-version=4.4.0
>> --with-binutils-version=2.19 --with-arch=armv5te
>> --with-sysroot=/home/jingyu/projects/gcc/toolchain_build/cupcake_rel_root
>> --with-gmp-version=4.2.4 --with-mpfr-version=2.4.1 --with-gdb-version=6.6
>> --program-transform-name='s,^,arm-eabi-,'
>> Thread model: single
>> gcc version 4.4.0 (GCC)
>>
>> (I am using the tool chain from the Google Android V1.5 open source
>> project - http://source.android.com/download.)
>>
>> Thanks,
>>
>>
>> Chris.
>>
>>
>>
>> --
>> Chris Isbell
>> Systems Integration Manager, CDSRail
>> Fareham, Hampshire, UK.
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>
>
>
next prev parent reply other threads:[~2009-10-26 12:41 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
2009-10-26 7:42 ` Chris Isbell
2009-10-26 8:27 ` Jello huang
2009-10-26 12:41 ` Tom [this message]
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=4AE598DD.3050107@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox