Summary: | haskell-cabal.eclass strips all binaries by default | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Gentoo's Haskell Language team <haskell> |
Status: | RESOLVED FIXED | ||
Severity: | QA | CC: | pesa |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 239866 |
Description
Diego Elio Pettenò (RETIRED)
2008-12-21 15:59:37 UTC
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. *** |