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.
*** Bug 251998 has been marked as a duplicate of this bug. ***
Upstream no longer maintains oer and rejected my patch (now split into two patches to be attached here). The reason for rejection given was:
On Sat, Aug 28, 2010 at 07:21:03PM +0300, EQU wrote:
> While I appreciate your efforts in improving oer, I must dissapoint
> you by telling that I do not, and have not, maintained oer since the
> year 2005 and I don't think that will change.
Created attachment 245161 [details, diff]
Fixes mangling of *FLAGS at the buildsystem level, adds --disable-strip
I added a --disable-strip option instead of removing it completely in hopes of making the patch upstreamable.
net-irc/oer removed as upstream abandoned it and there were bugs.