Summary: | Better way to explain the difference between make and emake. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Andrea Cerrito <is> |
Component: | Documentation | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | enhancement | CC: | lyralyra |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrea Cerrito
2004-02-11 00:39:05 UTC
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. |