Re: Problem compiling ROOT v5.32.00-rc2 with Python 2.6.4

From: Sébastien Gadrat <>
Date: Thu, 1 Dec 2011 12:00:01 +0100

Dear all,

Sorry for the missing information, and thank you for your quick and useful replies !

Your replies helped me to find out what was wrong with the compilation. As Win suggested, the problem was because ROOT was using a static library to compile ! However there is a lib on my system, but after checking the log file made at the configure step, I found out that ROOT did not find it, and then use a .a lib found in some other place.

The dynamic python lib is there:
$ ls /usr/local/python/python-2.6/lib/

However, for some reason, ROOT does not check this directory, and finally finds a .a lib:

   Found file
/usr/local/python/python-2.6/lib/python2.6/config/libpython2.6.a Checking if
/usr/local/python/python-2.6/lib/python2.6/config/libpython2.6.a is a 64-bit library
  objdump -a
/usr/local/python/python-2.6/lib/python2.6/config/libpython2.6.a | grep 'x86-64'
  result: 1
  is a 64bit library

I then have forced the right path for python lib, and the compilation went smoothly to the end ! Thanks Wim !

Best regards,


Le 30/11/2011 21:21, a écrit :
> Hi,
>> Apart from John's request, could you post the invocation of g++ for -o
>> lib/ (you did a parallel build, the line you quote is not
>> related to the error message).
> that error I've seen before, eons ago, for certain systems when
> linking with the
> libpython.a library instead of the .so. First question, then, is of
> course whether
> there isn't a .so on the system available? Second, for the .a, the
> extra flags of
> "-ldl -lpthread -lutil" are needed. Something must have died over the
> years if
> these aren't handed by configure or the makefile anymore.
> Best regards,
> Wim

Sébastien Gadrat
IN2P3/CNRS Computing Center - Lyon (FRANCE)
Tél. +33 (0)4 78 93 08 80

Received on Thu Dec 01 2011 - 12:00:11 CET

This archive was generated by hypermail 2.2.0 : Thu Dec 01 2011 - 17:50:01 CET