dev-haskell/c2hs-0.15.1:20081213-025446.log: * QA Notice: Pre-stripped files found: dev-haskell/c2hs-0.15.1:20081213-025446.log: * /var/tmp/portage/dev-haskell/c2hs-0.15.1/image/usr/bin/c2hs 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
Hi Diego, all haskell packages are compiled with ghc, and are then stripped. Keeping the symbols will do no good, as they are useless -- they come from generated code. It will not help debugging if the symbols are kept. What's the best way to proceed with this issue? It affects all haskell applications.
haskell-cabal.eclass: Don't strip executables, let portage do it. revision: 1.18 date: 2010-01-26 22:50:40 +0200 author: kolmodin; + if version_is_at_least "1.4" "$(cabal-version)"; then + # disable executable stripping for the executables, as portage will + # strip by itself, and pre-stripping gives a QA warning. + # cabal versions previous to 1.4 does not strip executables, and does + # not accept the flag. + # this fixes numerous bugs, amongst them; + # bug #251881, bug #251882, bug #251884, bug #251886, bug #299494 + cabalconf="${cabalconf} --disable-executable-stripping" + fi Preserving debug info can help in cases when package is built of both haskell and C sources mixed.
*** Bug 251882 has been marked as a duplicate of this bug. ***
*** Bug 251883 has been marked as a duplicate of this bug. ***
*** Bug 251884 has been marked as a duplicate of this bug. ***
*** Bug 251886 has been marked as a duplicate of this bug. ***
*** Bug 299494 has been marked as a duplicate of this bug. ***
