[U-Boot-Users] Conflicts in u-boot with different toolchains

Hello,
I work with an OMAP5912 OSK. I am trying to build u-boot 1.1.4 for the board but hitting some problems, while building and with the built binary.
I am using the ELDK toolchain that I have downloaded from www.denx.de, have installed both versions ELDK 3.1.1 (GCC-3.3.3 and GLIBC-2.3.1) and ELDK 4.0 (GCC-4.0.0 and GLIBC-2.3.5).
I am able to build u-boot-1.1.4. However the binary built using ELDK 4.0 toolchain doesn't boot the board. The same sources, when 'distcleaned' and built again using the ELDK 3.1.1 toolchain generates a binary that boots the OSK board.
I have made some changes in the u-boot-1.1.4 source code:
For the OMAP5912 OSK the flash drivers are not available. I need to configure CFI to provide the drivers for me. As a quick work around, I picked up the OSK flash drivers from u-boot-1.1.2 and added them for supporting flash on the OSK.
With the u-boot binary generated by the ELDK 3.1.1 toolchain, I can boot the board and the flash driver has also been tested. I have erased the flash, and written a JFFS2 filesystem to it. I am also able to boot out of the JFFS2 fileysystem.
Has anyone seen problems building u-boot-1.1.4 with ELDK 4.0 toolchain?
Further, with the ELDK 4.0 toolchain, I seem to be hitting more basic problems. for example, when I compile packages inetutils (this provides the network utilities like ftp, telnet servers and clients) it gives compilation error on some statements where there is type-casting. However, when the same inetutils sources are cleaned and built using the ELDK-3.1.1 toolchain, it builds without any issues. This seems more like a GCC-4.0.X issue as I've tested this same scenario with a crosstools toolchain (GCC-4.0.2) and have the same problems.
Thanks in advance,
Regards, Kanagesh
participants (1)
-
Kanagesh R