[Tutor] Installing gnome-python/conflicts with old python versions trouble

[ashleigh smythe]

Hello!  I'm trying to install gnome-python-1.99.16.  My Linux came with
python1.5 (in /usr/lib) but I installed python2.2 in /usr/local/lib. I'm
using 2.2 for all my python learning.  I read somewhere (Red Hat info?)
that I should leave the python1.5 on my system as Red Hat might need to
use it.  Of course that was _after_ I deleted some of the 1.5 files! 
Nevertheless, now when I try to install gnome-python, it seems like it
finds 2.2 but also 1.5 and gives me error messages indicating that my
python libraries are too old.  

I have had similar problems installing additional python modules as I'm
just not clear on where they (or frankly anything else I install!)
should go - I put biopython into /usr/local/lib/python2.2/site-packages
but python2.2 can't find my input files in my home directory, only if
they are also in /site-packages.

I tried some of the options offered in ./config -- help but they didn't
seem to help (but I could just be misunderstanding them as I am still
pretty lame with general Linux/bash stuff!).  

Long configure message after my ./config is below.

Thanks for any ideas/explanations!

Ashleigh

[ashleigh@nate gnome-python-1.99.16]$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
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 ANSI C... none needed
checking dependency style of gcc... gcc3
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking for a sed that does not truncate output... /bin/sed
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -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 dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC 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.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/bin/ld) supports shared libraries...
./configure: =$CC -shared $libobjs $deplibs $compiler_flags ${wl}-soname
$wl$soname -o $lib: command not found
yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether -lc should be explicitly linked in... no
creating libtool
checking for python... /usr/bin/python
checking for python version... 1.5
checking for python platform... linux-i386
checking for python script directory...
${prefix}/lib/python1.5/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python1.5/site-packages
checking for python >= 2.2... configure: error: too old