[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Linking problems with gdb-7.2



Hi,

I tried to build gdb with the patch in bug #579834 but got into problems
with the linker:

srs@kvm-hurd:~/DEBs/gdb/gdb-7.2/build/objdir/gdb$ i486-gnu-gcc -g
-D_GNU_SOURCE -o gdb gdb.o libgdb.a
-lreadline ../opcodes/libopcodes.a ../bfd/libbfd.a  ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -lshouldbeinlibc   -lncurses -lz -lm    -L/usr/lib/python2.6/config -lpthread -ldl -lutil -lm -lpython2.6 /usr/lib/libexpat.so ../libiberty/libiberty.a  gnulib/libgnu.a /lib/libmachuser.so.1 /lib/libhurduser.so.0.3 
libgdb.a(gnu-nat.o): In function `gnu_wait':
/home/srs/DEBs/gdb/gdb-7.2/gdb/gnu-nat.c:1583: undefined reference to
`prune_threads'
collect2: ld returned 1 exit status

prune_threads is undefined according to the above, but is defined in
libgdb.a:
nm libgdb.a |grep prune_threads 
         U prune_threads
00000a99 t prune_threads

This function is defined in threads.c bud does not seem to be recognized
by the linker. What is the difference with a symbol reported as "T" or
"t" ? According to the manpage for nm there does not seem to be any
difference between them:
"T"
"t" The symbol is in the text (code) section.


Reply to: