This is the mail archive of the
mailing list for the eCos project.
Re: How to build big-endian arm libraries for the Intel XScaleIXP425
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: Krishna Ganugapati <krishnag at marakicorp dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Mon, 23 Feb 2004 20:55:09 +0000
- Subject: Re: [ECOS] How to build big-endian arm libraries for the Intel XScaleIXP425
- References: <00a501c3fa49$082c1850$6401a8c0@KRISHNAGATEWAY>
Krishna Ganugapati wrote:
b.. gcc-3.2.1-arm-multilib.patch ------------> This should have been
warning enough. Its 2004 - perhaps Gary's patch of May 2003 has already
been folded appropriately into this patch... (speculative)
IIRC that patch would conflict with the arm multilib one because they
affect similar areas in the same file. Although if so I'd expect the
toolchain build to fail.
Anyway, the "official" way to build is to download
http://ecos.sourceware.org/gcc-3.2.1-arm-be.patch and apply that _after_
having applied gcc-3.2.1-arm-multilib.patch
The tools took some amount of time to build, but built flawlessly. All my
tools were stored in /gnutools on my machine.
I then fired up the configtool - changed the build path to /gnutools from
/opt/ecos/gnutools and surprise I saw the message "/gnutools does not appear
to contain the build tools - use this folder anyway?"
Did you see if there was anything in there? Did the toolchain build
Am I right in assuming that gcc-3.2.1-arm-multilib.patch that is provided
with the toolchain sources is a patch that generates all necessary binaries
and libraries for all variants of arm. More specifically, does this patch
once applied force generation of binaries and libraries necessary for
building a big-endian arm target for the Intel XScale IXP425? If this is
correct, my potential moral is now a real moral..
It doesn't include big-endian support.
Can I therefore assume that my binaries were successfully built
Nope. Look there and find out! In particular from the command line try
running "/gnutools/tools/bin/arm-elf-gcc -print-multi-lib" to see if
big-endian libraries are included.
Could someone kindly explain to me why this message pops up - the toolchain
is nicely installed in /gnutools - I point the "Build Path" to /gnutools -
is there anything else I need to do?
It probably means there aren't tools there ;-).
Could someone explain what gcc-3.2.1-arm-multilib.patch does? My reading of
diff files is poor.
It allows the compiler to support various alternative configurations, or
optimisations for certain configurations, specifically:
big-endian is another option, but is included in the separate patch above.
Might I humbly suggest that the website be updated to indicate that ecos2.0
toolchains do not provide the big-endian support for arm - presumably for
size reasons and how to go about building a big-endian toolchain?
The big-endian patch isn't mentioned in the instructions for rebuilding
tools, so I've added that.
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
>>>>> Visit us in booth 2527 at the Embedded Systems Conference 2004 <<<<<
March 30 - April 1, San Francisco http://www.esconline.com/electronicaUSA/
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss