dependency of GDB-6.8.50-27032009 on "libpython2.4"

dependency of GDB-6.8.50-27032009 on "libpython2.4"

[suma sharma]

Hi,
I have a m16cm32c toolchain, which I have used to compile the
following test case:
#include<stdio.h>

int main()
{
        int i=10, j=20, k;
        j++;
        if(j>20)
                printf("%d",j);
        else
                printf("%d",i);
        return 0;
}

I compiled the test case using the following command:
$ /usr/share/m16cm32c_elf-1/bin/m32c-elf-gcc test_gdb.c -msim -g -o test_gdb.out

I have built the gdb utility i.e. m32c-elf-gdb and m32c-elf-gdbtui
using GDB-6.8.50-27032009 on an FC5 system.
When I try debugging the output file " test_gdb.out" on FC7 using the
following command:
$./m32c-elf-gdbtui test_gdb.out
I get the following error:
--------------------------------------------------------------------------
./m32c-elf-gdbtui: error while loading shared libraries:
libpython2.4.so.1.0: cannot open shared object file: No such file or
directory
--------------------------------------------------------------------------

The FC5 system where the GDB was built has "libpython2.4.so" at
"/usr/lib", while the FC7 system where I am using the GDB for
debugging has "libpython2.5.so" at "/usr/lib".
Why does GDB-6.8.50-27032009 have a dependency on "libpython2.4",
whereas "GDB-6.8.50-11102009" doesn.t seem to have any such dependency
on any "libpython"? :(

Could anyone please help me?
Thanking you in advance.

Regards,
Sumasamyukta

Re: dependency of GDB-6.8.50-27032009 on "libpython2.4"

[Tom Tromey]

>>>>> ">" == suma sharma <sumasamyukta@gmail.com> writes:

>> The FC5 system where the GDB was built has "libpython2.4.so" at
>> "/usr/lib", while the FC7 system where I am using the GDB for
>> debugging has "libpython2.5.so" at "/usr/lib".
>> Why does GDB-6.8.50-27032009 have a dependency on "libpython2.4",
>> whereas "GDB-6.8.50-11102009" doesn.t seem to have any such dependency
>> on any "libpython"? :(

We added Python scripting capabilities to gdb during this period.

>> Could anyone please help me?

If you want to transport gdb binaries between different machines, you
have a couple of choices.  One choice is to make sure that the same
libraries are available everywhere.  Another one is to configure with
--disable-python.  This will make it so that gdb is not linked against
the python library.

Tom

Re: dependency of GDB-6.8.50-27032009 on "libpython2.4"

[Eli Zaretskii]

> Cc: gdb@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Thu, 21 May 2009 11:39:44 -0600
> 
> If you want to transport gdb binaries between different machines, you
> have a couple of choices.  One choice is to make sure that the same
> libraries are available everywhere.  Another one is to configure with
> --disable-python.  This will make it so that gdb is not linked against
> the python library.

Isn't a static link yet another possibility?

Re: dependency of GDB-6.8.50-27032009 on "libpython2.4"

[Tom Tromey]

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: gdb@sourceware.org
>> From: Tom Tromey <tromey@redhat.com>
>> Date: Thu, 21 May 2009 11:39:44 -0600
>> 
>> If you want to transport gdb binaries between different machines, you
>> have a couple of choices.  One choice is to make sure that the same
>> libraries are available everywhere.  Another one is to configure with
>> --disable-python.  This will make it so that gdb is not linked against
>> the python library.

Eli> Isn't a static link yet another possibility?

Sure.  In that case you have to build python yourself (at least Fedora
doesn't ship the static library) and you must also arrange for the
python runtime files to be installed in the correct place.

Tom

Re: dependency of GDB-6.8.50-27032009 on "libpython2.4"

[Eli Zaretskii]

> Cc: sumasamyukta@gmail.com, gdb@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Fri, 22 May 2009 10:59:38 -0600
> 
> Eli> Isn't a static link yet another possibility?
> 
> Sure.  In that case you have to build python yourself (at least Fedora
> doesn't ship the static library) and you must also arrange for the
> python runtime files to be installed in the correct place.

Right.

Btw, unless GDB needs a large portion of Python runtime, naming those
which are needed in README could also be helpful piece of information
for someone who wants to carry GDB on a memory stick.