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.
app-antivirus/f-prot-4.6.7:20081211-083548.log: * QA Notice: Pre-stripped files found:
app-antivirus/f-prot-4.6.7:20081211-083548.log: * /var/tmp/portage/app-antivirus/f-prot-4.6.7/image/opt/f-prot/f-prot
This is a binary ebuild, so there is not much that we can do here but ignoring the QA check.
We can set QA_PRESTRIPPED ;)
/me goes to read
- app-antivirus/f-prot-6.0.2 (masked by: package.mask)
# Fabian Groffen <email@example.com> (06 Mar 2010)
# Masked for security issues and discontinued interest from upstream to
# support non-Windows platforms. Bug #233928
# Pending removal on April 6, 2010
Then, for now, it isn't usefull to correct it... Why not to close this bug ?