A friend of mine point me to notice that some ebuilds are using make instead of emake: I didn't know why, until, using emake instead of make, some ebuilds started to fail (ie: nagios-plugins). The only difference I saw between make and emake is that emake handles the MAKEOPTS var of make.conf, make it does not. If it's correct, I suggest to explain this difference ie in the make.conf, to avoid people to force the -j feature and run into troubles. Reproducible: Always Steps to Reproduce: Expected Results: ie: # MAKEOPTS provides extra options that may be passed to 'emake' (not make: # not all programs may use extra options, and some builds will fail if # you try to use parallel makes) when a program is compiled. # Presently the only use is for specifying the number of parallel # makes (-j) to perform. The suggested number for parallel makes is # CPUs+1.
why should the end user care about make/emake ?
Some users asked me (I'm an italian forum moderator) if they had to open a bug report because some ebuilds didn't compile by default using MAKEOPTS var. Besides "end user", I think the difference care a noob portage developer (other users tried to modify an ebuild that started to fail).
personally i think all ebuilds should use `emake` if they fail to build with -j, then you change the command to `emake -j1` then there wouldnt be this problem
As spanky said.
