public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Gene Smith <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: undefined reference to `set_breakpoint'
Date: Wed, 17 Mar 2010 17:34:00 -0000	[thread overview]
Message-ID: <hnpq6u$ehm$1@dough.gmane.org> (raw)

With CVS head, see this error when, I think, linking gdb:

rm -f gdb
gcc -g -O2      \
                 -o gdb gdb.o libgdb.a \
                   ../sim/arm/libsim.a ../readline/libreadline.a 
../opcodes/libopcodes.a ../bfd/libbfd.a  ../libiberty/libiberty.a 
../libdecnumber/libdecnumber.a   ../libgui/src/libgui.a 
-L/home/gene/addons/insight-cvs/insight_build/tk/unix -ltk8.4 
-L/home/gene/addons/insight-cvs/insight_build/tcl/unix -ltcl8.4   -lX11 
-ldl  -lieee -lm -lncurses -lz -lm     -lpython2.6 -lexpat 
../libiberty/libiberty.a  gnulib/libgnu.a
libgdb.a(gdbtk-bp.o): In function `gdb_set_bp':
/home/gene/addons/insight-cvs/insight_build/gdb/../../insight_sources/gdb/gdbtk/generic/gdbtk-bp.c:533: 
undefined reference to `set_breakpoint'

Configured like this:
configure -v --quiet --prefix=$PREFIX \
    --target=$TARGET --enable-interwork --enable-multilib \
    --with-gnu-ld --with-gnu-as \
    --disable-werror

Is this due to a missing package? This is on 64bit fedora 12. tk and tcl 
dev packages installed.

Thanks,
-gene

             reply	other threads:[~2010-03-17  5:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 17:34 Gene Smith [this message]
2010-03-17 17:57 ` Tom Tromey
2010-03-18  3:39   ` Keith Seitz
2010-03-18  4:58     ` Gene Smith
2010-03-19  4:32     ` Gene Smith
2010-03-20  5:33       ` Hui Zhu
2010-03-30  8:29         ` Hui Zhu
2010-03-30 16:48           ` Hui Zhu
2010-03-31  3:20             ` Keith Seitz
2010-03-31  4:12               ` Hui Zhu
2010-03-31  4:28                 ` Keith Seitz
2010-03-31  5:33                   ` Hui Zhu
2010-03-31  5:37                     ` Keith Seitz

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='hnpq6u$ehm$1@dough.gmane.org' \
    --to=gds@chartertn.net \
    --cc=insight@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).