tested emake and remove die after econf.
Created attachment 258171 [details, diff] Ebuild patch
(In reply to comment #0) > tested emake On what hardware? How many CPUs? MAKEOPTS set to what value? > and remove die after econf. And this is useful because?
(In reply to comment #2) > On what hardware? How many CPUs? MAKEOPTS set to what value? Core 2 Duo, 2 cpu, makeopts -j5 > And this is useful because? from http://devmanual.gentoo.org/quickstart/index.html Next, a function named src_compile. Portage will call this function when it wants to compile the package. The econf function is a wrapper for calling ./configure, and emake is a wrapper for make. In the case of emake, the common || die "something went wrong" idiom is used — this is to ensure that if for some reason an error occurs, Portage will stop rather than trying to continue with the install. Note that econf does not need the || die idiom, as it dies by itself if something failed.
(In reply to comment #2) >MAKEOPTS set to what value? Tested on another machine with MAKEOPTS="-j12"
+*audacious-2.5_alpha1 (30 Jan 2011) + + 30 Jan 2011; Tony Vroon <chainsaw@gentoo.org> +audacious-2.5_alpha1.ebuild: + This is to become 2.5 with time. Masked for your protection. If you unmask & + use this, note that bugs go upstream at http://jira.atheme.org/ for the + Audacious or Audacious-Plugins project as appropriate. Replace make with + emake as suggested by Agostino "ago" Sarubbo in bug #349858.
+*audacious-plugins-2.5_alpha1 (30 Jan 2011) + + 30 Jan 2011; Tony Vroon <chainsaw@gentoo.org> + +audacious-plugins-2.5_alpha1.ebuild: + This is to become 2.5 with time. Masked for your protection. If you unmask & + use this, note that bugs go upstream at http://jira.atheme.org/ for the + Audacious or Audacious-Plugins project as appropriate. Replace make with + emake as suggested by Agostino "ago" Sarubbo in bug #349858.
