| Summary: | emerge of python 2.4.1 segfaults when using gcc 4.0.1 and CFLAG -fomit-frame-pointer | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Danoz <danoz-gentoo> |
| Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | flash3001 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| URL: | http://forums.gentoo.org/viewtopic-t-385623.html | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Danoz
2005-09-29 22:34:13 UTC
try gcc-4.0.2 some problem here he difference is that i have gcc-4.0.2 the same problem occurs with the new python 2.4.2 ebuild. i havent tested gcc 4.0.2 yet though. (In reply to comment #2) > some problem here he difference is that i have gcc-4.0.2 And your CFLAGS? Could you try with a sane set of CFLAGS, something like "-O2 -march=pentium3 -fomit-frame-pointer -pipe". I personally have not had the problems described here yet, and I haven't heard from others that I know to be running gcc-4 describing this problem. I get the same with python 2.4.2. Mabey its's because I use glibc-2.3.5-r3. Mabey I should use glibc-2.3.5.20050421 or newer my flags: CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" get back to us |