From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Hall <halla3@corp.earthlink.net>
Cc: gdb@sources.redhat.com
Subject: Re: compile error on solaris 8 and 2.6
Date: Wed, 20 Oct 2004 19:17:00 -0000 [thread overview]
Message-ID: <20041020174438.GE3527@gnat.com> (raw)
In-Reply-To: <1098287184.27340.41.camel@flagg>
> While trying to compile gdb on Solaris 8 and 2.6 I get the following
> error:
>
> 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 -ltermcap
> -lsocket -lnsl -lm -liconv ../libiberty/libiberty.a
> Undefined first referenced
> symbol in file
> wattr_on libgdb.a(tui-wingeneral.o)
> wattr_off libgdb.a(tui-wingeneral.o)
> ld: fatal: Symbol referencing errors. No output written to gdb
> collect2: ld returned 1 exit status
> make[1]: *** [gdb] Error 1
> make[1]: Leaving directory `/netapp/home/halla3/gdb-6.2.1/gdb'
> make: *** [all-gdb] Error 2
> bash-2.03$
I am not sure exactly what the problem is, but I'll give you some
ideas: These symbols are used for TUI, a text-based interface for
GDB. As a temporary measure, you should be able to get rid of this
error by configuring GDB without TUI: --disable-tui.
I remember having experienced some problems building TUI myself
on sparc-solaris or mips-irix, because I use a local installation
of ncurses. So the configure script sort of picks up ncurses library,
but still uses the .h files in /usr/include. So I get a discrepancy
between what the compiler thinks is available in my ncurses library,
and what is actually there. And I also get undefined symbols. I don't
know if it's possible to make it work or not (I think Michael Chastain
tried on Tru64), but you could try by adding -I/path/to/ncurses/include
to your CFLAGS (make CFLAGS='-g -O2 -I/blablabla).
Maybe it's a bona fide omission in our configure script. It's hard to
tell without knowing more about your environment. But since I don't use
TUI, I never spent the time looking into this. I just build without TUI.
Good luck,
--
Joel
next prev parent reply other threads:[~2004-10-20 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 18:34 Andrew Hall
2004-10-20 19:17 ` Joel Brobecker [this message]
2004-10-20 19:44 ` Michael Chastain
2004-10-20 20:11 ` Joel Brobecker
2004-10-20 20:26 ` Michael Chastain
2004-10-20 20:29 ` Andrew Hall
2004-10-20 21:19 ` Andrew Hall
2004-10-20 21:22 ` Michael Chastain
2004-10-20 21:36 ` Andrew Hall
2004-10-20 21:46 ` Andrew Hall
2004-10-20 23:11 ` Michael Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041020174438.GE3527@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb@sources.redhat.com \
--cc=halla3@corp.earthlink.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox