Bug 8923 - Linker (ld) Error During GDB Build
Summary: Linker (ld) Error During GDB Build
Alias: None
Product: gdb
Classification: Unclassified
Component: build (show other bugs)
Version: 6.3
: P1 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
: 8719 8731 8924 (view as bug list)
Depends on:
Reported: 2004-11-24 01:48 UTC by tdineen
Modified: 2011-11-18 15:54 UTC (History)
4 users (show)

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description tdineen 2004-11-24 01:48:00 UTC
[Converted from Gnats 1818]

Gentle People:

I get the following Linker Error when I run the make
on gdb 6.3 on Solaris 8 0n Sparc.

Can anyone give me some indication od what I did wrong?

Thomas Dineen

r: creating libgdb.a
ranlib libgdb.a
rm -f gdb
gcc -g -O2 \
-o gdb gdb.o libgdb.a \
../bfd/libbfd.a ../readline/libreadline.a ../opcodes/libopcodes.a ../libiberty/libiberty.a -ldl -lncurses -lsocket -lnsl -lm ../libiberty/libiberty.a
Undefined first referenced
symbol in file
initscr32 libgdb.a(tui.o)
w32attron libgdb.a(tui-wingeneral.o)
w32attroff libgdb.a(tui-wingeneral.o)
getcurx libgdb.a(tui-io.o)
getcury libgdb.a(tui-io.o)
acs32map libgdb.a(tui-win.o)
w32addch libgdb.a(tui-io.o)
ld: fatal: Symbol referencing errors. No output written to gdb
collect2: ld returned 1 exit status
*** Error code 1
make: Fatal error: Command failed for target ‘gdb’
Current working directory /export/home/tools/gdb/gdb-6.3/gdb-6.3/gdb
*** Error code 1
make: Fatal error: Command failed for target ‘all-gdb’

gdb 6.3

Solaris 8 Sparc

Please Contact me for assistance.
Comment 1 tdineen 2004-11-24 01:48:00 UTC
Please help.
Comment 2 Tom Tromey 2011-11-18 15:52:09 UTC
I think this probably fixed.
There have been various configury fixes in the last 7 years related
to curses, termcap, etc.
If you try a newer release and it is still broken, please re-open.
Comment 3 Tom Tromey 2011-11-18 15:53:44 UTC
*** Bug 8719 has been marked as a duplicate of this bug. ***
Comment 4 Tom Tromey 2011-11-18 15:54:23 UTC
*** Bug 8731 has been marked as a duplicate of this bug. ***