Originally Posted by randomizer
I don't know if CONCURRENCY_LEVEL actually does much in this case. I would think that the makeflags defined in /etc/makepkg.conf would determine the number of jobs anyway.
No it works, I've used it ever since I found it and it worked on Arch too. It's what I've always used when doing kernels, I could try the -j4 one but I never remember.
 If you think about it, makepkg shouldn't be directly tied to make. It also shouldn't default to multiple threads, that would bunk compatibility with single core machines. Yes they exist! In all my Arch time nothing compiled with multiple threads until I told it to do so. I don't find it odd either, due to mentioned compatibility.
[final edit due to sleep] I'm going to be heading out after this, but I thought I'd add one last bit. A lot of the debate behind CONCURRENCY_LEVEL is that it might be machine specific, which also applies to -jX as well. Some have said it doesn't do much for kernel compilation, while others say it does. I found it used more of my cores, in fact it used all of them at 100%. That would make me to believe it would be doing more work and reducing times, though I didn't try 1/2/3/4, I just set it to 4. Either way it helped me, so I'm going to keep using it. Whether or not it helps you is entirely different, though it doesn't hurt to try it.Edited by mushroomboy - 1/16/11 at 12:13am