sys-apps/byld-1.0.3:20081219-171934.log: * QA Notice: Pre-stripped files found:
sys-apps/byld-1.0.3:20081219-171934.log: * /var/tmp/portage/sys-apps/byld-1.0.3/image/usr/lib/byld/packages/BIN/Joe/joe
sys-apps/byld-1.0.3:20081219-171934.log: * /var/tmp/portage/sys-apps/byld-1.0.3/image/usr/lib/byld/packages/BIN/Vim/vim
sys-apps/byld-1.0.3:20081219-171934.log: * /var/tmp/portage/sys-apps/byld-1.0.3/image/usr/lib/byld/packages/BIN/Base/bash
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.
byld installs binaries to run "on the target" that shouldnt be stripped