Summary: | Patch to filter -fomit-frame-pointers from AbiWord | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Masover <ninja> |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | codergeek42 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
patch to abiword-2.0.10.ebuild
patch to abiword-2.0.10.ebuild |
Description
David Masover
2004-08-30 19:32:32 UTC
Created attachment 38554 [details, diff]
patch to abiword-2.0.10.ebuild
filters -fomit-frame-pointer from AbiWord, thus fixing an issue of CRASH on
copy/paste.
Created attachment 38555 [details, diff]
patch to abiword-2.0.10.ebuild
oops, above patch is reversed. This fixes it.
i need more reports to put such a restriction in. Shouldn't this be up to the user, since those flags cause problems with debugging on most packages. Yes, those flags do cause problems with debugging. They also cause the program to crash for me. Hence they are removed. I can duplicate the crash on two separate machines. If anyone wants to try, go ahead -- try my CFLAGS. I would love to have this be more specific -- maybe -fomit-frame-pointer doesn't get along with -Os? Still, I'd rather it have a _very_minor_ optimization removed so that it works for everyone, and then add it back in if it's really needed. sorry,seems I didn't finish my thought :), I compiled with -fomit-frame-pointer here to test and didn't have that proplem. If it ends up being a combination of different cflags, then it is sadly the users issue. I'll try a bit to find that combo, then. How hard is it to filter a combo from cflags? Why does it become the user's issue -- weren't my cflags sane? I'll go away if someone gives me per-package cflag settings and I can post big warnings in the forum about this issue. Just to check...are you sure it's not the size-optimization (-Os) that's doing it? Does it get fixed if you use CFLAGS such as "-O2 -march=athlon-xp -fomit-frame-pointer"? And considering that the most recent 2.0 release is 2.0.14 (latest in Portage is 2.0.11), does upgrading help? We're not going to filter all possible flag combinations, unless we can get multiple reports from a flag causing known breakage. Your CFLAGS are sane - try with i686 and -O2 maybe - but this doesn't mean we need to filter omit-fp for everyone. |