+++ This bug was initially created as a clone of Bug #258114 +++
Some notes on ROOT:
* The idea behind ROOT is that one can build a system with ROOT=/somewhere and
then chroot into it or tar up /somewhere as a system image. It is not designed
to allow the user to run /somewhere/usr/bin/foo.
* ROOT can't be used correctly in src_*, since ROOT might be different when
merging a binary package. For example, a binary package might be built with
ROOT=/ and then installed onto a system using ROOT=/somewhere.
* ROOT isn't used for library dependencies. When building, libraries, headers
etc. on / have to be used. Cross-compiling etc is done by configuring the
toolchain correctly, not by hacking ebuilds in a way that breaks binary
See also the discussion on bug #167285 for more info.
Suggest the fix. That variable is used and unfortunately generated files have paths hardcoded into them.
if the buildsystem hardcodes the location of the binaries, then that is still independant of ROOT. ROOT only allows the installation of a binary into a different directory. they are not meant to be run "from there" - they are meant to be run where the root of the system is ROOT (ie. chroot $ROOT)
just strip it away. the point of ROOT is that you should be able chroot into it and then call the binaries - so adding ROOT to the paths wont work correctly.
again - ROOT might be set at install time, for packages which have been built on a entirely different machine (with a different ROOT set)...
the latest version doesnt use it anymore - so punting the old ebuilds would also do it.