Hi Hanni,
Distcc would be especially useful to test out 'out-of-the-box'
successful toolchain compilations - it takes approximately 10 (failure)
- 50 (success) minutes for me to test toolchain builds on x86
To take into account every permutation of libc, binutils,
kernel-headers, and gcc version - it could easily approach a week or
more on a uniprocessor system!
It would likely also be entirely possible to integrate that into the
buildroot itself if one had access to several similar architectures
running an instance of the chroot.
The script is really huge - I'm currently still in the middle of trying
to wrap my head around all of the toolchain-specific files / directories
/ subsystems that are required to mount / create / destroy upon chroot /
exit.
I'll send you the script, and please try it out - no license information
is included (b/c at the moment it is still alpha) but will surely be
available by the free-est GPL or BSD license.
It's good to hear that you could see the value in this too!!
~/Chris
Hanni Ali wrote:
Sounds fascinating and potentially a very useful tool.
I would be keen to integrate distcc support into it to allow faster builds,
I would be happy to work on that aspect of the script if you like.
Hanni
--
[email protected] mailing list
