Problem ./configure with libpythonv2.6

Asked by philippe.steer

Hello

I obtained an error when I tried to install esys-particle on my computer with an ubuntu 8.04 os. I have successfully followed all the installation steps until .configure where I got this message:

checking for Py_Main in -lpython2.6... no
configure: error: Library libpython2.6 library not found.

I have reinstalled mpi and pythonv2.6 and I still get this error message (and eventually I don't get the make program). If someone know how to deal with this problem, I wil be happy to hear

Best regards

Philippe

PS: here is the entire configure procedure

root@actinote:/usr/logiciels/esys-particle# ./configure CC=mpicc CXX=mpic++ --without-epydoc
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... gawk
checking whether make sets $(MAKE)... yes
checking for cppunit-config... /usr/bin/cppunit-config
checking for Cppunit - version >= 1.10.0... 1.12.1
checking for a Python interpreter with version >= 2.3... python
checking for python... /usr/bin/python
checking for python version... 2.6
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.6/dist-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.6/dist-packages
checking for vtkpython... /usr/bin/vtkpython
configure: "VTK root dir = /usr"
checking for povray... /usr/bin/povray
configure: "PovRay root dir = /usr"
checking for epydoc... /usr/bin/epydoc
configure: "Epydoc root dir = "
checking for C++ compiler default output file name... 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 mpic++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of mpic++... gcc3
checking whether we are using the GNU C compiler... yes
checking whether mpicc accepts -g... yes
checking for mpicc option to accept ISO C89... none needed
checking dependency style of mpicc... gcc3
checking how to run the C preprocessor... mpicc -E
checking for flex... no
checking for lex... no
checking for bison... no
checking for byacc... no
checking whether ln -s works... yes
checking for find... find
checking for laminfo... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
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 mpicc... /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 the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
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 ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from mpicc object... ok
checking for ANSI C header files... no
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 whether we are using the GNU C++ compiler... (cached) yes
checking whether mpic++ accepts -g... (cached) yes
checking dependency style of mpic++... (cached) gcc3
checking how to run the C++ preprocessor... mpic++ -E
checking for objdir... .libs
checking if mpicc supports -fno-rtti -fno-exceptions... no
checking for mpicc option to produce PIC... -fPIC -DPIC
checking if mpicc PIC flag -fPIC -DPIC works... yes
checking if mpicc static flag -static works... yes
checking if mpicc supports -c -o file.o... yes
checking if mpicc supports -c -o file.o... (cached) yes
checking whether the mpicc linker (/usr/bin/ld) 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 for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
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
checking for ld used by mpic++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the mpic++ linker (/usr/bin/ld) supports shared libraries... yes
checking for mpic++ option to produce PIC... -fPIC -DPIC
checking if mpic++ PIC flag -fPIC -DPIC works... yes
checking if mpic++ static flag -static works... yes
checking if mpic++ supports -c -o file.o... yes
checking if mpic++ supports -c -o file.o... (cached) yes
checking whether the mpic++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
7
checking for Py_Main in -lpython2.6... no
configure: error: Library libpython2.6 library not found.
root@actinote:/usr/logiciels/esys-particle#

Question information

Language:
English Edit question
Status:
Solved
For:
ESyS-Particle Edit question
Assignee:
No assignee Edit question
Solved by:
Dion Weatherley
Solved:
Last query:
Last reply:
Revision history for this message
Best Dion Weatherley (d-weatherley) said :
#1

Hi Philippe,

I haven't seen this error before. Did you install python2.6-dev as well as python2.6? Try "sudo apt-get install python2.6-dev" then re-run "sh autogen.sh" and then re-try "./configure". I've successfully installed ESyS-Particle on Ubuntu 8.04 many times so I suspect you are missing some headers or libraries.

In case you did not see it, I've written an FAQ specifically about installing ESyS-Particle in Ubuntu:
https://answers.launchpad.net/esys-particle/+faq/261

From memory I wrote these notes whilst installing ESyS-Particle on Ubuntu-8.04.

I hope this helps.

Cheers,

Dion.

Revision history for this message
philippe.steer (philippe-steer) said :
#2

Thanks Dion Weatherley, that solved my question.

Revision history for this message
philippe.steer (philippe-steer) said :
#3

I had to install python2.6 -dev