This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: trying tx49 ref4955 design
- From: "e.stiebler" <emu at ecubics dot com>
- To: Andrew Lunn <andrew at lunn dot ch>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 15 Feb 2006 11:00:36 -0700
- Subject: Re: [ECOS] trying tx49 ref4955 design
- References: <43F365B9.1070400@ecubics.com> <20060215174456.GR10349@lunn.ch>
Andrew Lunn wrote:
libgcc.a is provided by the compiler. It looks like libgcc.a is
compiled using a different Application Binary Interface than what eCos
was compiled with.
Try looking at the options you can pass to the configure script when
you build the tool chain. Is there anything to control the ABI it
uses?
I used pretty much what's on the "building toolchain" webpage.
So setting :
ECOS_REPOSITORY=/AD1/MIRRORS/Mirror.Linux/ECOS/ecos/packages ; export
ECOS_REPOSITORY
ECOS_GNUTOOLS=/AD1/SHARED/ECOS/gnutools ; export ECOS_GNUTOOLS
ECOS_TARGET=mips-tx49-elf ; export ECOS_TARGET
I compile binutils with :
#!/bin/sh
../binutils-2.16.1/configure \
--target=$ECOS_TARGET \
--prefix=$ECOS_GNUTOOLS/$ECOS_TARGET
make all
make info
make install
and gcc with:
#!/bin/sh
../gcc-3.4.4/configure \
--target=$ECOS_TARGET \
--with-gnu-as \
--with-gnu-ld \
--with-newlib \
--enable-languages="c,c++" \
--prefix=$ECOS_GNUTOOLS/$ECOS_TARGET \
--with-gxx-include-dir=$ECOS_GNUTOOLS/$ECOS_TARGET/include
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss