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. Thanks, Diego
Are these bug reports generated by a badly automated script or something? *** This bug has been marked as a duplicate of bug 251981 ***
Mostly, I was expecting the packages to be revbumped, so I checked all the currently-merged stripped files on my tinderbox and reported the missing ones, I didn't expect them to be fixed without revbump.
(In reply to comment #2) > Mostly, I was expecting the packages to be revbumped, so I checked all the > currently-merged stripped files on my tinderbox and reported the missing ones, > I didn't expect them to be fixed without revbump. Ah. I figured going through an entire revbump / stabilisation loop would be too much hassle for these (mostly ancient) ebuilds as well as for the arch teams.
