A limitation of our current build scripts makes it impossible to build the Python libraries without building the Python extension. This means that you either have to install python-dev or python-devel or something like that, or run ./configure --without-py
--David Michael Greene wrote: > The package might be called something different depending on what > system you are on, but it looks like you need the 'python-dev' > package, or whatever supplies Python headers on your system. The > stock Python install often will not give you these. > > Suhail Doshi <[email protected]> wrote: >> Seems to spiral down at this point now: >> >> BUILD SUCCESSFUL >> Total time: 0 seconds >> make[4]: Leaving directory `/home/hadoop/thrift/lib/java' >> make[3]: Nothing to be done for `install-data-am'. >> make[3]: Leaving directory `/home/hadoop/thrift/lib/java' >> make[2]: Leaving directory `/home/hadoop/thrift/lib/java' >> Making install in py >> make[2]: Entering directory `/home/hadoop/thrift/lib/py' >> /usr/bin/python setup.py build >> running build >> running build_py >> running build_ext >> building 'thrift.protocol.fastbinary' extension >> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall >> -Wstrict-prototypes -fPIC -I/usr/include/python2.5 -c >> src/protocol/fastbinary.c -o >> build/temp.linux-x86_64-2.5/src/protocol/fastbinary.o >> src/protocol/fastbinary.c:13:20: error: Python.h: No such file or directory >> src/protocol/fastbinary.c:14:23: error: cStringIO.h: No such file or >> directory >> src/protocol/fastbinary.c:116: error: expected specifier-qualifier-list >> before 'PyObject'
