On Mon, Aug 06, 2012 at 08:53:42AM -0700, Tom Warren wrote:
Seems like f414d013c5e129e66c04ff699bd60b34894d3d38 breaks a lot of builds with the stock Ubuntu linaro toolchain, e.g.
$ ./MAKEALL jornada Configuring for jornada board... make: *** [jornada_config] Error 1 arm-linux-gnueabi-size: './u-boot': No such file make: *** No rule to make target `include/autoconf.mk', needed by `depend'. Stop. make: *** Waiting for unfinished jobs....
--------------------- SUMMARY ---------------------------- Boards compiled: 1 Boards with warnings but no errors: 1 ( jornada )
The .MAKELOG is empty and the .ERR says:
make: *** No rule to make target `include/autoconf.mk', needed by `depend'. Sto p. make: *** Waiting for unfinished jobs....
Here's my log using linaro 4.6.2 on my Ubuntu 10.04LTS dev system:
$ arm-linux-gnueabi-gcc --version arm-linux-gnueabi-gcc (Ubuntu/Linaro 4.6.2-14ubuntu2~ppa1) 4.6.2 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ printenv CROSS_COMPILE arm-linux-gnueabi-
$ ./MAKEALL jornada Configuring for jornada board... text data bss dec hex filename 131282 2724 4596 138602 21d6a ./u-boot
--------------------- SUMMARY ---------------------------- Boards compiled: 1
$
I don't see the same warning - in fact it builds fine. I always run an ARM MAKEALL before submitting a pull request, using my default (4.4.1) toolchain.
Allen did the SPL work - adding him for comment.
I'm trying to reproduce now. f414d013c5e129e66c04ff699bd60b34894d3d38 only changes the generation of include/config.mk. When it fails does include/config.mk get generated and does it look correct?
-Allen