dev-lang/fpc-ide-2.2.2:20081213-084315.log: * QA Notice: Pre-stripped files found: dev-lang/fpc-ide-2.2.2:20081213-084315.log: * /var/tmp/portage/dev-lang/fpc-ide-2.2.2/image/usr/bin/fp 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
The default behaviour of fpc is to strip executables. There's a warning in the fpc pkg_postinst that you may want to remove -Xs from /etc/fpc.cfg because of this, but since this affects the behaviour of fpc outside of ebuilds as well, this is not done automatically. I don't think there's anything to fix here, but if you have any suggestions, please share.
No comment, so closing.
Should at least set QA_PRESTRIPPED, although a stripped default is not something I sincerely like enormously...
Having taken another look, it turns out to be easy enough to use a different config file for the build of fpc-ide (and lazarus), so now fpc continues to strip executables by default outside of portage, but not here. No need for QA_* additions and all those warnings anymore :)
