Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: gdb@sources.redhat.com
Subject: Re: tcl cannot build 64bit.
Date: Tue, 09 Mar 2004 21:20:00 -0000	[thread overview]
Message-ID: <404E3539.8010005@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0403092047350.5833@lazy>

> When I build GDB 6.1 CVS version as a 64bit binary, the tclsh fails to
> build. The linker complains "skipping incompatible
> /home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a when searching
> for -ltcl8.4" even though libtcl8.4.a is availale in that directory.
> 
> When I force it to link with the archive I get a bunch of  undefined
> reference to ".symbol" as follows: ( I am only pasting a few). And they
> look like glibc symbols...

GDB or expect?  GDB doesn't need tcl.  The expect in the repository is 
sufficiently out-of-date to be getting dangerous :-(  I'd just use "make 
all-gdb".

Andrew



  reply	other threads:[~2004-03-09 21:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 21:10 Manoj Iyer
2004-03-09 21:20 ` Andrew Cagney [this message]
2004-03-09 21:34   ` Manoj Iyer
2004-03-09 22:03     ` Andreas Schwab
2004-03-09 22:05   ` Andreas Schwab
2004-03-09 22:27     ` Andrew Cagney
2004-03-09 22:55       ` Andreas Schwab
2004-03-10  1:34         ` Andrew Cagney
2004-03-10  5:46           ` Manoj Iyer
2004-03-10  9:13             ` Andreas Schwab
2004-03-10  9:12           ` Andreas Schwab
2004-03-10 15:25             ` Ian Lance Taylor
2004-03-10 16:02               ` Andreas Schwab
2004-03-10 16:05                 ` Daniel Jacobowitz
2004-03-10 16:11                   ` Manoj Iyer
2004-03-10 17:22                     ` Andreas Schwab
2004-03-10 17:30                       ` Ian Lance Taylor
2004-03-12 22:26                       ` Manoj Iyer
2004-03-16 23:50                       ` Andrew Cagney

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=404E3539.8010005@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=manjo@austin.ibm.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