Robin Becker schrieb am 22.08.2014 um 17:50: > I'm trying to build a bunch of extensions in a 2.7 virtual environment on a > centos 7 VM. I don't know centos very well and I understand centos 7 is > quite new > >> building 'lxml.etree' extension >> >> creating build/temp.linux-x86_64-2.7 >> >> creating build/temp.linux-x86_64-2.7/src >> >> creating build/temp.linux-x86_64-2.7/src/lxml >> >> gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall >> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong >> --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic >> -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall >> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong >> --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic >> -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/libxml2 >> -I/home/rptlab/website/xxx/xxx_0/build/lxml/src/lxml/includes >> -I/usr/include/python2.7 -c src/lxml/lxml.etree.c -o >> build/temp.linux-x86_64-2.7/src/lxml/lxml.etree.o -w >> >> {standard input}: Assembler messages: >> >> {standard input}:1858223: Error: unknown pseudo-op: `.' >> >> gcc: internal compiler error: Killed (program cc1) >> >> Please submit a full bug report, >> >> with preprocessed source if appropriate. >> >> See <http://bugzilla.redhat.com/bugzilla> for instructions. >> >> error: command 'gcc' failed with exit status 4 > > > uname -a >> Linux localhost.localdomain 3.10.0-123.6.3.el7.x86_64 #1 SMP Wed Aug 6 >> 21:12:36 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > > > gcc --version >> gcc (GCC) 4.8.2 20140120 (Red Hat 4.8.2-16) >> Copyright (C) 2013 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. There is NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > I do have the various devel rpms installed so far as I can tell. > > Has anyone else seen this error? It's entirely possible that it might be I > don't have enough memory or something
Yes, that's most likely it. Having 500MB+ of free(!) RAM is a good idea for the build. > lxml builds almost always take a long time. For testing, you can speed things up quite substantially by using "-O0" as your CFLAGS. Not a good idea for a production system, though. You might also get away with building a (static?) wheel on another compatible Linux system that has more RAM. Stefan -- https://mail.python.org/mailman/listinfo/python-list