Ok,
during compiling I have found another makefile with the same problem: the makefile into busybox don't download busybox !
Apart from that, the compilation end without error.
But the raspberry don't boot
With the file passed from you it don't start.
I have followed the directives at this link:
http://elinux.org/RPi_Software and downloaded the original 3 files from here
https://github.com/raspberrypi/firmware/tree/master/boot:
1) bootcode.bin
2) start.elf
3) fixup.dat
With this only files and the kernel compiled, the RPI boot, but hangup with the error:
Failed to execute /init
Kernel panic - not syncing: no init found
Before hangup, there are also a warning: unable to open an initial console.
Maybe there are some things in the kernel configuration that is not good !
Have you some ideas about ?
In any case,
I would like exchange ideas with you about the approach and future development of the bfw porting on RPi.
Firstly, if I have undestand, you have make a "standalone" from scratch cross compiling system for ARM. This is a good idea because your system is completely indipendent of the system where is "hosted" the cross compiling system, but, in my opinion, is a rigid system, because if I want compiling for example only one package, I must recompiling all.
I am not sure of this, but this is my opinion and I would like to know your point of view about this.
My idea on this point, before see your solution, was another: I thought it might have been from the development system of BFW 2.32 and only changing the directive of GCC before starting the compilation ...
I have a BFW development system based on a slackware 11 (see my post
http://www.brazilfw.com.br/forum/viewtopic.php?f=3&t=86867#p313298 and I have frequently used for compiling only one new packet: working fine.
Maybe it can be used for compiling a new version of BFW 2.32 for ARM ... if this solution is praticable, we will have a simply and quickly solution for porting BFW onto RPi ....
Secondly, developing your approach, we need implement the adding of other packets and thinking to an semi-automated system for compiling (and simply adding to the working system) of new software packages ... is a good challenge (and a considerable amount of work).
In this case is my opinion that maybe can be more simple starting from a basic distro where we can have also other software that normaly is not included in BFW. For example in my home, I have a system where I running BFW vitualized on a debian base system where I running also asterisk, apache web server and a NAS ... On RPi, as sayed, is not possible to run vbox, but if we run a small linux system with some other things of the normal BFW version ... maybe can be more attractive.
But for now and firstly of all ... I thinking that is need to investigate the way this kernel don't boot !!!
Emilio