[U-Boot-Users] make env

[Ladislav Michl]

On Thu, Mar 20, 2008 at 09:02:58PM +0100, Wolfgang Denk wrote:
> Yes, and actually I think this is correct. What we're building is a
> target Linux application, so the U-Boto specific CFLAG settings have
> no meaning for this (or rather would be just dangerous).
> 
> Example:
> 
> -> make env
> make -C tools/env all MTD_VERSION= || exit 1
> make[1]: Entering directory `/home/wd/git/u-boot/work/tools/env'
> ln -s ../../lib_generic/crc32.c crc32.c
> make[1]: Leaving directory `/home/wd/git/u-boot/work/tools/env'
> make[1]: Entering directory `/home/wd/git/u-boot/work/tools/env'
> arm-linux-gcc -Wall -DUSE_HOSTCC crc32.c  fw_env.c  fw_env_main.c -o
> fw_printenv
> make[1]: Leaving directory `/home/wd/git/u-boot/work/tools/env'
> -> file tools/env/fw_printenv
> tools/env/fw_printenv: ELF 32-bit LSB executable, ARM, version 1, dynamically linked (uses shared libs), for GNU/Linux 2.4.3, not stripped
> 
> I'm not sure what you wanted to express with your comment?

Well, it seems you have "properly" configured toolchain - you installed
proper kernel headers. In my case it ends with:

-> make env CROSS_COMPILE=arm-C411_L24-linux-gnu-
make -C tools/env all MTD_VERSION= || exit 1
make[1]: Entering directory `/home/ladis/src/u-boot/tools/env'
arm-C411_L24-linux-gnu-gcc -Wall -DUSE_HOSTCC crc32.c  fw_env.c
fw_env_main.c -o fw_printenv
fw_env.c:39:27: error: mtd/mtd-user.h: No such file or directory

Here I have no opportunity to tell compiler where to find that header.
I'd have to put them on some "standard" place, which could conflict with
2.4 headers. I do not want to pass U-Boot specific flags, just fw_setenv
specific.

Best regards,
	ladis