> I can build Python 2.2.1 just fine on my Solaris 2.8 machine using gcc > 3.1.1 and binutils 2.12.1 > > If I install either binutils 2.13 or the just-released gcc 3.2, I can > no longer build Python -- it dumps core quite far into the build process. > > I don't really have a clue as to whether it's a gcc problem, a binutils > problem, or a Python problem. Any suggestions as to how to proceed? I haven't heard this before. I guess gcc 3.2 is brand new? I'm not generally following gcc releases except from hearsay. I suppose you *did* do a "make clean" before trying with a different compiler? Maybe even re-run configure. If that doesn't help, try turning off optimization (edit the generated Makefile to delete the "-O3" option, them make clean). If that helps, it must be a gcc optimizer problem. If that doesn't help, it's still most likely to be a gcc or binutils problem. A SourceForge bug report might be in order regardless. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4