
Hi Tom and Jeroen,
On Mon, 20 Oct 2014 21:01:47 +0200 Jeroen Hofstee jeroen@myspectrum.nl wrote:
Hello Masahiro,
On 19-10-14 16:28, Jeroen Hofstee wrote:
Hello Tom,
On 01-10-14 17:31, Jeroen Hofstee wrote:
On 30-09-14 03:29, Tom Everett wrote:
I am getting this compile error:
scripts/Makefile.build:55: /tank/home/tom/freebsd/uboot/u-boot-2014.10-rc2/board/amd/sunxi/Makefile: >>> No such file or directory
gmake[1]: *** No rule to make target `/tank/home/tom/freebsd/uboot/u-boot-2014.10-rc2/board/amd/sunxi/Makefile'. >>> Stop.
It appears that the dir "/board/amd/sunxi" does not exist. It >>> should be "/board/sunxi".
I stumbled upon the same problem, on FreeBSD, the root user seems to have an VENDOR=amd env hanging around, hence u-boot's Makefile cannot assign the correct value. (or it would need override at least).
I have a hard time understanding what exactly is going on here. It has nothing to do with the type of shell / OS. e.g. linux/bash behaves exactly the same with:
export VENDOR=toasted make wandboard_quad_config all
scripts/Makefile.build:55: /home/jeroen/software/u-boot/board/toasted/wandboard/Makefile: No such file or directory make[1]: *** No rule to make target `/home/jeroen/software/u-boot/board/toasted/wandboard/Makefile'. Stop.
The slightly shorter (in time) version below, shows similar behavior. make distclean wandboard_quad_config include/config.h && cat include/config.h
This would make sense if I did `make VENDOR=toasted`, but that is not the case. Can you shed some light on this, how does make end up using the version of the original shell? And how can that be prevented?
Sorry, this seems a bug.
Can you please check if this patch solve your problem? http://patchwork.ozlabs.org/patch/401315/
Best Regards Masahiro Yamada