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.
Created attachment 248971 [details]
Fixed in -r4
+*signing-party-1.1.3-r4 (15 Oct 2010)
+ 15 Oct 2010; Dane Smith <email@example.com>
+ +signing-party-1.1.3-r4.ebuild, +files/signing-party-makefile.diff:
+ Rebump for signing-party. Address lack of LDFLAGS respect wrt bug 339124,
+ prevention of pre-stripping files wrt bug 339125, lack of jobserver
+ and numbers other simple QA fixes.