title: No rule to make target `libpython2.6.a'
body: <p>I am trying to compile Python2.6 from its source codes, and took steps as follow, and encountered an error message:</p>
  
  <pre><code>./configure
  ...
  [root@KuGouIdc Python-2.6.6]# ls
  config.log                                 Demo        Makefile.pre                       Objects                                     Python
  config.status                              Doc         Makefile.pre.in                    Parser                                      README
  configure                                  Grammar     Makefile.pre.in.cflags             PC                                          RISCOS
  configure.in                               Include     Makefile.pre.in.fix-parallel-make  PCbuild                                     setup.py
  configure.in.check-for-XML_SetHashSalt     install-sh  Makefile.pre.in.lib64              pyconfig.h                                  setup.py.add-RPATH-to-pyexpat
  configure.in.disable-pymalloc-on-valgrind  Lib         Makefile.pre.in.no-static-lib      pyconfig.h.in                               setup.py.expat
  configure.in.expat                         LICENSE     Makefile.pre.in.systemtap          pyconfig.h.in.disable-pymalloc-on-valgrind  setup.py.lib64
  configure.in.rpath                         Mac         Misc                               pyconfig.h.in.systemtap                     systemtap-example.stp
  configure.in.systemtap                     Makefile    Modules                            pyfuntop.stp                                Tools
  [root@KuGouIdc Python-2.6.6]# make -n all
  gcc -pthread -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes  -I. -IInclude -I./Include   -DPy_BUILD_CORE -o Modules/python.o ./Modules/python.c
  make: *** No rule to make target `libpython2.6.a', needed by `python'.  Stop.
  </code></pre>
  
  <p>I reviewed the Makefile detail, and really could not find any rule to make the target 'libpythonXXX.a'. I googled around, and it seemed that no one had encountered the same issue as me?</p>
  
  <p>In the Makefile, it really has a rule for making the target 'libpythonXXX.so'.</p>