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.
For what concerns pre-built packages, you should set the QA_PRESTRIPPED variable in the ebuild with the list of known pre-stripped objects in the package.
Diego, there's already Bug 306591 about it, see my comments and patch there. I managed to work around most of those issue, but really unsure whether it's worth fixing until a rewrite which doesn't involve bigloo is finished upstream. Basically, this all is bigloo fault here and fixing leads to completely fugly ebuild b/c, well, bigloo is just that stupid.
*** This bug has been marked as a duplicate of bug 306591 ***