Bug 658016 – net-libs/nodejs-6.11.5 on ppc - src_install(): npm stalls indefinitely

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description ernsteiswuerfel 2018-06-12 22:27:29 UTC]

Created attachment 535760 [details]
emerge --info

Running a tatt-rdeps check for bug #653116 pulled in net-libs/nodejs-6.11.5 as latest stable for ppc. Building seems fine, but at install stage it stalls indefinitely running npm at 100 % load (for about 3 hours now):

make: Leaving directory '/var/tmp/portage/net-libs/nodejs-6.11.5/work/node-v6.11.5/out'
>>> Source compiled.
 * Skipping make test/check due to ebuild restriction.
>>> Test phase [disabled because of RESTRICT=test]: net-libs/nodejs-6.11.5

>>> Install nodejs-6.11.5 into /var/tmp/portage/net-libs/nodejs-6.11.5/image/ category net-libs
make -j3 -l2 install DESTDIR=/var/tmp/portage/net-libs/nodejs-6.11.5/image/ 
make -C out BUILDTYPE=Release V=1
make[1]: Entering directory '/var/tmp/portage/net-libs/nodejs-6.11.5/work/node-v6.11.5/out'
  touch 174e1924ee03965071fe65426addc8c0233f1418.intermediate
  LD_LIBRARY_PATH=/var/tmp/portage/net-libs/nodejs-6.11.5/work/node-v6.11.5/out/Release/lib.host:/var/tmp/portage/net-libs/nodejs-6.11.5/work/node-v6.11.5/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../deps/v8_inspector/third_party/v8_inspector/platform/v8_inspector; mkdir -p /var/tmp/portage/net-libs/nodejs-6.11.5/work/node-v6.11.5/out/Release/obj/gen/blink/platform/v8_inspector/public/protocol /var/tmp/portage/net-libs/nodejs-6.11.5/work/node-v6.11.5/out/Release/obj/gen/blink/platform/v8_inspector/protocol /var/tmp/portage/net-libs/nodejs-6.11.5/work/node-v6.11.5/out/Release/obj/gen/blink/platform/inspector_protocol; python ../inspector_protocol/CodeGenerator.py --output_base "/var/tmp/portage/net-libs/nodejs-6.11.5/work/node-v6.11.5/out/Release/obj/gen/blink/platform" --config inspector_protocol_config_stl.json
rm 174e1924ee03965071fe65426addc8c0233f1418.intermediate
make[1]: Leaving directory '/var/tmp/portage/net-libs/nodejs-6.11.5/work/node-v6.11.5/out'
if [ ! -r node -o ! -L node ]; then ln -fs out/Release/node node; fi
/usr/bin/python2.7 tools/install.py install '/var/tmp/portage/net-libs/nodejs-6.11.5/image/' '/usr'
 * PT_PAX marking -m /var/tmp/portage/net-libs/nodejs-6.11.5/image/usr/bin/node with scanelf
 * XATTR_PAX marking -me /var/tmp/portage/net-libs/nodejs-6.11.5/image/usr/bin/node with setfattr

[Comment 1 ernsteiswuerfel 2018-08-30 16:41:22 UTC]

Will close as invalid as I can't reproduce this behavious on my current stable ppc setup.

# emerge --info
Portage 2.3.40 (python 3.6.5-final-0, default/linux/powerpc/ppc64/17.0/32bit-userland/desktop/gnome/systemd, gcc-7.3.0, glibc-2.25-r11, 4.14.67-gentoo ppc64)
=================================================================
System uname: Linux-4.14.67-gentoo-ppc64-PPC970FX,_altivec_supported-with-gentoo-2.4.1
KiB Mem:     8098712 total,   7068392 free
KiB Swap:    9439224 total,   9439224 free
Timestamp of repository gentoo: Fri, 24 Aug 2018 20:30:01 +0000
Head commit of repository gentoo: 89e07cccc1e6492289dfd476f988379f9085c408
sh bash 4.4_p12
ld GNU ld (Gentoo 2.30 p2) 2.30.0
distcc 3.2rc1 powerpc-unknown-linux-gnu [disabled]
app-shells/bash:          4.4_p12::gentoo
dev-lang/perl:            5.24.3-r1::gentoo
dev-lang/python:          2.7.14-r1::gentoo, 3.6.5::gentoo
dev-util/cmake:           3.9.6::gentoo
dev-util/pkgconfig:       0.29.2::gentoo
sys-apps/baselayout:      2.4.1-r2::gentoo
sys-apps/sandbox:         2.13::gentoo
sys-devel/autoconf:       2.13::gentoo, 2.69-r4::gentoo
sys-devel/automake:       1.15.1-r2::gentoo
sys-devel/binutils:       2.29.1-r1::gentoo, 2.30-r2::gentoo
sys-devel/gcc:            7.3.0-r3::gentoo
sys-devel/gcc-config:     1.8-r1::gentoo
sys-devel/libtool:        2.4.6-r3::gentoo
sys-devel/make:           4.2.1-r3::gentoo
sys-kernel/linux-headers: 4.13::gentoo (virtual/os-headers)
sys-libs/glibc:           2.25-r11::gentoo

[Comment 2 Jeroen Roovers (RETIRED) 2018-08-31 10:46:47 UTC]

I think it was valid at the time.