Message226953
> i really dont know how to fix it
It's a GCC bug, not a Python bug: "gcc: Internal error: ...".
What is your OS? What is your GCC version? How much memory do you have?
Do you get the same error if you run "make" again?
Try to run "gcc -pthread -c -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -I./Include -DPy_BUILD_CORE -o Objects/unicodeobject.o" again.
Do you modify MAKEFLAGS to set -j to run GCC in parallel?
Usually, you can workaround GCC bugs by disabling optimizations. You can try to modify Makefile to replace "-O3" with "-O2" or even "-O0" (disable all optimizations), and then try to run "make" again.
Again, it's not a Python bug, but a GCC bug, probably already fixed in a more recent GCC version (the latest is 4.9.1):
https://gcc.gnu.org/ |
|
Date |
User |
Action |
Args |
2014-09-16 14:44:31 | vstinner | set | recipients:
+ vstinner |
2014-09-16 14:44:31 | vstinner | set | messageid: <1410878671.2.0.251456958698.issue22424@psf.upfronthosting.co.za> |
2014-09-16 14:44:31 | vstinner | link | issue22424 messages |
2014-09-16 14:44:30 | vstinner | create | |
|