View Single Post
Old 10-16-2012, 09:16 AM   #690
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,837
Karma: 6314522
Join Date: Feb 2012
Device: Too many.
U-boot needs to be configured for the target machine.
So other than selecting the proper configuration target from the u-boot in the K5 source bundle rather than the u-boot configuration from the DX source bundle . . . .

This should 'just work':
http://www.mobileread.com/forums/sho...&postcount=276

Once you make (no pun intended) that happen, then you can go about modifying the source code.
Just be sure to do a 'make clean' before the 'make <..._config> ; make' step after any changes even though the build scripting does a full dependency test.

The cross-compilers for Windows and for Linux are posted in the DIY-KeK environment pool. If running MacOSx, probably running a Linux LiveCD is the best idea.

Also follow this thread:
http://www.mobileread.com/forums/sho...d.php?t=194025
Although it does not apply to building u-boot, it could be used for that purpose.
The reason being that the build scripting forces an "application's gcc" to function as a "standalone (bare metal) gcc"

Last edited by knc1; 10-16-2012 at 11:06 AM.
knc1 is online now   Reply With Quote