The source package contains more than 10,000 .c files, and a total amount of +60,000 files, add to that the intermediate files and you can start realizing the magnitudes we are talking about.
I found it interesting... Cheers, Connie
$ tar xf /var/portage/distfiles/gcc-4.3.3.tar.bz2 $ find gcc-4.3.3/ -name \*.c|wc -l 11926 $ find gcc-4.3.3/ -name \*|wc -l 61659
- first, gcc is compiled using whatever compiler you have on your system
- second, gcc is re-compiled using the gcc version that you just compiled
- third, gcc is recompiled again using the gcc produced on the second step, then both are compared (the third and the second) to see if they are 1:1 the same and that there's no problem.
Now you can start wondering how the number of intermediate files is really huge.
And don't forget that in if you have multilib enabled two entire are created for 32 and , that means that gcc will be recompiled 6 times, and will double the total number of files once again.
Why does a build create so many temporary files?
'via Blog this'