Portage warns about pre-stripped files being installed into the image directory; this is a bad thing since it makes Portage's splitdebug feature useless, and it stops the users and the developers from looking into backtraces with full debug information available.
For the developers going to look into it, what you have to look out for, to
find what is stripping the files, is one of these conditions:
- explicit "strip" command run on the produced files;
- "install -s" command to install the binary files;
- "-Wl,-s" flag passed during linking
Remove the "strip" commands, remove the "-s" option at install, and remove
"-Wl,-s" and the problem should be gone.
Um, that's a tough one - the stripped (ELF) binary it does install is the pre-compiled one in bin/, not the local executable.
*** Bug 251980 has been marked as a duplicate of this bug. ***
The ebuild no longer installs the prebuilt Linux binary, so portage should no longer complain about stripped files having been found.