coreutils-8.20 failed [SOLVED]

[symon1980]

help2man: can't get '--help' info from man/arch.td/arch
make[2]: *** [man/arch.1] Error 127
make[2]: *** Waiting for unfinished jobs....
help2man: can't get '--help' info from man/uname.td/uname
make[2]: *** [man/uname.1] Error 127
make[2]: Leaving directory `/var/tmp/portage/sys-apps/coreutils-8.20/work/coreutils-8.20'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/sys-apps/coreutils-8.20/work/coreutils-8.20'
make: *** [all] Error 2
emake failed
* ERROR: sys-apps/coreutils-8.20 failed (compile phase):
* emake failed
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 2394: Called __eapi2_src_compile
* phase-helpers.sh, line 612: Called die
* The specific snippet of code:
* emake || die "emake failed"




After performing an emerge --update --ask world

Any ideas?

[Pilsner]

Same error here:

Code: Select all

Linux gent 3.5.7-gentoo #1 Mon Oct 22 11:33:30 MSK 2012 x86_64 Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz GenuineIntel GNU/Linux

[mhanft]

Same error here on both of my Gentoo computers:

Code: Select all

Linux n 3.5.7-gentoo #1 SMP Sun Nov 4 17:16:04 CET 2012 i686 Intel(R) Xeon(R) CPU X5690 @ 3.47GHz GenuineIntel GNU/Linux
Linux fileserver 3.5.7-gentoo #2 SMP PREEMPT Sun Nov 4 17:40:42 CET 2012 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux

[Pilsner]

Found in bugzilla https://bugs.gentoo.org/show_bug.cgi?id=446438, compiles ok with MAKEOPTS="-j1".

[Rhywek]

Wouldn't it be a good idea if some ebuilds would themselves know that they need MAKEOPTS="-j1"?

I'm running into this issue often with various packages - they compile only with MAKEOPTS="-j1". Therefore I just have it in my make.conf, which is far from ideal, because other packages that can use MAKEOPTS="-j9" compile much slower than they could. I know I could only set MAKEOPTS="-j1" sometimes when something goes wrong, but I don't have time for getting compile problems, researching them, and fixing them manually.

Just like ebuilds can filter compile flags, couldn't they also filter make flags?

[mhanft]

Just for the records: "-j1" does work on both my Gentoo computers. Didn't know that this seems to be a common workaround...

Thank you for the "-j1" pointer

[symon1980]

arrghhhh

I don't want to have to configure my settings to "-j1"

any other workarounds?

[vokiel]

arrghhhh

I don't want to have to configure my settings to "-j1"

any other workarounds?

You don't have to just do:

Code: Select all

MAKEOPTS="-j1" emerge sys-apps/coreutils

on the command line

[Hu]

Wouldn't it be a good idea if some ebuilds would themselves know that they need MAKEOPTS="-j1"?

Yes, but it is a better idea if someone fixes the build system to work properly without requiring -j1. Many ebuilds already do force non-parallel builds. Search for emake -j1 (correct way to disable parallel) or \<make\> (wrong way to disable parallel) in the tree.

[symon1980]

arrghhhh

I don't want to have to configure my settings to "-j1"

any other workarounds?

You don't have to just do:

Code: Select all

MAKEOPTS="-j1" emerge sys-apps/coreutils

on the command line

I thought arghhh screw it... i'll try your suggestion "MAKEOPTS="-j1" emerge sys-apps/coreutils"
then started a world update and all seems ok "so far"
I'm up for a hell of an update with Kde 4.8.4 though... this may take a few hours.... i'm going to bed. LoL

will post back

[Robol]

You don't have to just do:

Code: Select all

MAKEOPTS="-j1" emerge sys-apps/coreutils

Thank you. It works

[Usermind42]

Thank you Pilsner.

[symon1980]

Yep that did the trick.... Thanx.

I only wonder if this will cause any future stability/speed issues....

[krinn]

Read the bug report, you'll see it was little trick for man pages, i'm quiet sure no instabilities will comes from dropping a manpages patch that wasn't working

[To]

There's nothing similar to package.use for this?

[motosauro]

Same problem and same solution here
thx

Edit: bugzilla's last entry says that it's been fixed in the portage tree, I didn't check though

[BobWya]

Hi all,

Thanks for the handy work around!! Very timely!!

Having been put on to potential benefits of LTO (from an on-line blog) and how to switch off LTO for specific packages that don't support link time optimisation - when using gcc 4.7.x...

It's much easier to create a file:

Code: Select all

/etc/portage/env/make-j1.conf

Code: Select all

MAKEOPTS="-j1"

Then you can specify packages that require single threaded making in the standard portage environment file:

Code: Select all

/etc/portage/package.env

Code: Select all

sys-apps/coreutils make-j1.conf

From the portage man page:

Code: Select all

...
                    package.env
                     Per-package environment variable settings. Entries refer to environment files that are placed in the /etc/portage/env/ directory and have the same format as
                     make.conf(5).

                     Format:
                     - comment lines begin with # (no inline comments)
                     - one DEPEND atom per line followed by name(s) of environment file(s)

                     Example:
                     # use environment variables from /etc/portage/env/glibc.conf for the glibc package
                     sys-libs/glibc glibc.conf
...

Anyone know what other packages need single threaded making? I've got some packages that are reverted to no-LTO - but could this be due to needing single-threading??

Thanks
Bob