On Tue, 22 Apr 2003, Eliasson, Anders (IndSys, GEFanuc, VMIC) wrote:
I'm attempting to build u-boot for the evb64260 brd. I'm doing so on a WinNT4 host with a Cygwin environment and a powerpc-elf cross compiler ( a Linux env is not an option ). This is fun but it's become apparent that I don't know what the heck I'm doing :^). Most of my problems seem to occur as a result of include files missing, in the wrong place, or incorrect. Here's an example of warnings/errors;
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++ make[1]: Entering directory `/cygdrive/d/uboot/uboot030/post/cpu' make[1]: `.depend' is up to date. make[1]: Leaving directory `/cygdrive/d/uboot/uboot030/post/cpu' make[1]: Entering directory `/cygdrive/d/uboot/uboot030/examples' make[1]: `.depend' is up to date. make[1]: Leaving directory `/cygdrive/d/uboot/uboot030/examples' make[1]: Entering directory `/cygdrive/d/uboot/uboot030/tools' gcc -Wall -pedantic -I../include -I.. -DTEXT_BASE=0xfff00000 -DUSE_HOSTCC -O
Please note that u-boot contains code that is supposed to run on the build host (rather than on the target), so you also need a native cygwin compiler which creates code for your x86-WinNT box. The "tools" directory above is such a directory containg tools for the host.
On a regular Linux system, you usually call the make like this:
make CROSS_COMPILE=powerpc-linux- all
The Makefiles then know where to use the "$(CROSS_COMPILE)gcc" and where to use the regular host "gcc". Be sure not to mix that up.
In general, I see no reason why u-boot should not be compilable under Cygwin. Getting there can well be a bit bumpy, though :-)
Regards, Marius
----------------------------------------------------------------------------- Marius Groeger SYSGO Real-Time Solutions AG mgroeger@sysgo.de Software Engineering Embedded and Real-Time Software www.sysgo.de Voice: +49-6136-9948-0 Am Pfaffenstein 14 www.osek.de FAX: +49-6136-9948-10 55270 Klein-Winternheim, Germany www.elinos.com