Activity log for bug #286334
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2008-10-20 10:33:37 | Roger Binns | bug | added bug | ||
| 2008-10-20 12:39:01 | Matthias Klose | gcc-defaults: status | New | Incomplete | |
| 2008-10-20 12:39:01 | Matthias Klose | gcc-defaults: statusexplanation | probably will close as won't fix. does lowering the optimization level will help? does gcc-4.1 or gcc-4.2 dow work better for you? | ||
| 2008-11-05 19:41:34 | Kees Cook | gcc-defaults: status | Incomplete | Won't Fix | |
| 2008-11-05 19:41:34 | Kees Cook | gcc-defaults: assignee | kees | ||
| 2008-11-05 19:41:34 | Kees Cook | gcc-defaults: statusexplanation | probably will close as won't fix. does lowering the optimization level will help? does gcc-4.1 or gcc-4.2 dow work better for you? | Marking as "Won't Fix" since this is an issue with the unpackaged python 2.3 source (and how it interacts with the Intrepid gcc). Short of fixing the realpath usage, the workaround mentioned (-D_FORTIFY_SOURCE=0) is right. |
