(Or -U_FORTIFY_SOURCE) See https://wiki.ubuntu.com/CompilerFlags for
more details.
--
gcc crashes python 2.3 in intrepid
https://bugs.launchpad.net/bugs/286334
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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.
** Changed in: gcc-defaults (Ubuntu)
Assignee: (unassigned) => Kees C
Thanks for the other workaround. The real bug is that gcc 4.3 with
FORTIFY causes a binary to fail if there could be a buffer overrun, not
if there definitely is one.
--
gcc crashes python 2.3 in intrepid
https://bugs.launchpad.net/bugs/286334
You received this bug notification because you are a
There's a workaround without disabling optimization:
http://orip.org/2008/10/building-python-235-on-ubuntu-intrepid.html
Short version: add BASECFLAGS=-U_FORTIFY_SOURCE to the 'configure'
command line.
--
gcc crashes python 2.3 in intrepid
https://bugs.launchpad.net/bugs/286334
You received this
As an addendum the workaround above only works during an early part of
the build process. The full process fails with the same error above.
Heck it even fails with -DPATH_MAX=16384. My conclusion is that the
code in stdlib.h is pointlessly causing a failure without looking at the
actual size of t
It works just under gcc-4.2. If I use -O0 under gcc-4.3 then it is also
fine, but even -O1 is sufficient for the crash.
$ ./configure CC=gcc-4.2 # works
$ ./configure OPT="-g -O0" # works
$ ./configure OPT="-g -O1" # splat
Running gdb on the binary I get this:
(gdb) bt
#0 0
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?
** Changed in: gcc-defaults (Ubuntu)
Status: New => Incomplete
--
gcc crashes python 2.3 in intrepid
https://bugs.launchpad.net/bugs/286334
You received this
