STINNER Victor added the comment: > 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/ ---------- nosy: +haypo -165559672 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22424> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
