aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorlandley <landley@69ca8d6d-28ef-0310-b511-8ec308f3f277>2005-07-28 19:38:52 +0000
committerlandley <landley@69ca8d6d-28ef-0310-b511-8ec308f3f277>2005-07-28 19:38:52 +0000
commitc7444d704193ba89f522d4e0ce8e5933beec793d (patch)
tree3840ac77ae5abb717763426cbce8a212095c3bf3 /docs
parentdbcb8958266ccf757d5c29db0cade9c702f944de (diff)
downloadbusybox-w32-c7444d704193ba89f522d4e0ce8e5933beec793d.tar.gz
busybox-w32-c7444d704193ba89f522d4e0ce8e5933beec793d.tar.bz2
busybox-w32-c7444d704193ba89f522d4e0ce8e5933beec793d.zip
From Rich Paul:
I've noticed that when I compile busybox on my laptop, it compiles more slowly than one would expect, and although it's a (more-or-less) multiprocessor system and I use -j5, make never seems to run more than one job at a time. I believe I have found the culprit:  each time a file is compiled, gcc runs about 5 times.  This is because the $(check_gcc) macros and the TARGET_ARCH macros are late binding. The attached patch cuts the compilation time by 66%, from 1.5 minutes to 30 seconds.  Your mileage may very.  These statements have not been evaluated by the FDA. git-svn-id: svn://busybox.net/trunk/busybox@10945 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions