emerge -u ruby-glib2 ... >>> Install ruby-glib2-0.16.0 into /var/tmp/portage/dev-ruby/ruby-glib2-0.16.0/image/ category dev-ruby make[1]: Entering directory `/tmp/portage/dev-ruby/ruby-glib2-0.16.0/work/ruby-gnome2-all-0.16.0/glib/src' /bin/install -c -m 0755 glib2.so /var/tmp/portage/dev-ruby/ruby-glib2-0.16.0/image//usr/lib64/ruby/site_ruby/1.8/x86_64-linux make[1]: /bin/install: Command not found make[1]: *** [/var/tmp/portage/dev-ruby/ruby-glib2-0.16.0/image//usr/lib64/ruby/site_ruby/1.8/x86_64-linux/glib2.so] Error 127 make[1]: Leaving directory `/tmp/portage/dev-ruby/ruby-glib2-0.16.0/work/ruby-gnome2-all-0.16.0/glib/src' make: *** [install] Error 2 !!! ERROR: dev-ruby/ruby-glib2-0.16.0 failed. # which install /usr/bin/install Reproducible: Always Steps to Reproduce: 1. emerge =dev-ruby/ruby-glib2-0.16.0 Actual Results: Install phase fails. Expected Results: Package upgraded successfully. # equery belongs /usr/bin/install [ Searching for file(s) /usr/bin/install in *... ] sys-apps/coreutils-6.7-r1 (/usr/bin/install) I am upgrading this package from 0.14.1 - obviously that version installed successfully - so presumably this is a recently introduced bug in the makefile. Creating a symlink from /usr/bin/install to /bin/install is a successful work-around.
Please search; yet another dupe of Bug 159922
*** This bug has been marked as a duplicate of bug 159922 ***
