出于我自己的原因，我在Debian Wheezy的源代码中安装了python3.3。我想为它添加一些模块，包括pygobject（gi.repository等）。我想要的大多数软件已经在python3.2（Wheezy上的默认python3）的同一台机器上工作和安装。
我可以将python3.3指向通用/usr/lib/python3/dist-packages来通过操作PYTHONPATH来获取已经安装的python3.2代码，但是（当然？）无法正确导入。所以，我想我需要从python3.3的源代码构建pygobject。
获取了pygobject的Wheezy源包后，我尝试了以下操作，将配置指向下载的pygobject目录中的python3.3安装和可执行文件：
$ PYTHON=/usr/local/bin/python3.3
$ export PYTHON
$ ./configure --prefix=/usr/local
输出如下：
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for some Win32 platform... no
checking for native Win32... no
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... dlltool
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating ./config.lt
config.lt: creating libtool
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking whether gcc and cc understand -c and -o together... yes
checking whether /usr/local/bin/python3.3 version >= 2.5.2... yes
checking for /usr/local/bin/python3.3 version... 3.3
checking for /usr/local/bin/python3.3 platform... linux
checking for /usr/local/bin/python3.3 script directory... ${prefix}/lib/python3.3/site-packages
checking for /usr/local/bin/python3.3 extension module directory... ${exec_prefix}/lib/python3.3/site-packages
checking for /usr/local/bin/python3.3 >= 3.1... yes
checking for python version... (cached) 3.3
checking for python platform... (cached) linux
checking for python script directory... (cached) ${prefix}/lib/python3.3/site-packages
checking for python extension module directory... (cached) ${exec_prefix}/lib/python3.3/site-packages
checking for headers required to compile python extensions... not found
configure: error: Python headers not found
我已经检查过安装了包python-dev和python3-dev，但当然这些包分别用于python2.7和python3.2的默认Wheezy pythons。那么，如何更改配置以获取python3.3的正确标头？
如果它是相关的，确切的版本号如下：python-3.3.6，pygobject-3.2.2。
答案 0 :(得分：2)
构建目录中的config.log文件对于对此进行排序非常有用。
python3.3标头安装在/usr/local/include/python3.3m中，但pygobject构建过程在/usr/local/include/python3.3（缺少m）的错误位置查找。要纠正此问题，配置需要调整环境标志：
$ PYTHON=/usr/local/bin/python3.3
$ export PYTHON
$ CPPFLAGS=-I/usr/local/include/python3.3m
$ export CPPFLAGS
$ ./configure --prefix=/usr/local
无法找到库时的其他问题可以通过配置PKG_CONFIG_PATH来解决，如果需要指定多个，请使用冒号作为分隔符（有关示例，请参阅answers to this question）。在Debian上，在成功运行./configure：
$ PKG_CONFIG_PATH=/usr/lib/pkgconfig
$ export PKG_CONFIG_PATH