In building toolchain it would be good to test if CONFIG_EXTERNAL_KERNEL_TREE exists at the very beginning

[GoogleCodeExporter]

While experementing with building firmware I found out that in building 
toolchain there is no test if external kernel tree 
(CONFIG_EXTERNAL_KERNEL_TREE) really exists

When it comes out that this kernel tree does not exist (default value of this 
variable points to someplace inside lly's homepage, witch does not exist on my 
computer :-) ) it is too late to change this config value, all the building 
should be started from the begining.

This test, with brief explanation where to change this value, will save several 
hours to all novice builders, so more of them will have chance to became 
contributors :-)

Original issue reported on code.google.com by dh...@nataraj.su on 6 Jan 2014 at 8:40

[GoogleCodeExporter]

toolchain rebuild procedure isn't intended for end/novice users. Please use 
prebuild version.

Anyway, if someone provide patch for build scripts, we will gladly accept it.

Original comment by lly.dev on 11 Jan 2014 at 7:50

• Added labels: Component-Scripts, Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Prebuilt version causes ld segfault for me. :-)

May be I will try to offer you a patch and may be some wiki article. 

Original comment by dh...@nataraj.su on 11 Jan 2014 at 7:57

[GoogleCodeExporter]

Which host OS (distro/version) you are using?

Original comment by lly.dev on 13 Jan 2014 at 8:33

[GoogleCodeExporter]

Debian, both Wheezy and Jessie, gives same effect

// I don not compleatly understand how does toolchanin binaries should be 
compatible with libraries installed on my desktop, so I do not know what to 
check if prebuild toolchan is compatible with my building environment 

Original comment by dh...@nataraj.su on 13 Jan 2014 at 8:38