public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Peter Choi <peter_tkchoi@yahoo.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Compilation of GDB6.3 [NEDD HELP]
Date: Fri, 04 Nov 2005 03:40:00 -0000	[thread overview]
Message-ID: <20051104034035.1064.qmail@web32908.mail.mud.yahoo.com> (raw)
In-Reply-To: <20051104031946.GA21903@nevyn.them.org>

Hi,

  I can't locate any build.log log file, but when I
check my "config.log", I found there was a error
message saying :

configure:1510: checking for libthread_db
configure:1531: gcc -o conftest -g -O2   conftest.c 
-lthread_db 1>&5
configure:1596: gcc -o conftest -g -O2   -rdynamic
conftest.c  -lthread_db 1>&5
/usr/lib/gcc-lib/i386-redhat-linux/3.3.2/../../../libthread_db.so:
undefined reference to `ps_pdwrite'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.2/../../../libthread_db.so:
undefined reference to `ps_pglobal_lookup'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.2/../../../libthread_db.so:
undefined reference to `ps_lsetfpregs'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.2/../../../libthread_db.so:
undefined reference to `ps_getpid'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.2/../../../libthread_db.so:
undefined reference to `ps_lsetregs'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.2/../../../libthread_db.so:
undefined reference to `ps_pdread'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.2/../../../libthread_db.so:
undefined reference to `ps_lgetfpregs'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.2/../../../libthread_db.so:
undefined reference to `ps_lgetregs'
collect2: ld returned 1 exit status
configure: failed program was:
#line 1589 "configure"
#include "confdefs.h"

int main() {

; return 0; }


  I wonder what cause this problem with my
"libthread_db" library???? Where should those variable
"ps_XXXX" reside???

  Please advise.

Regards.
Peter Choi


--- Daniel Jacobowitz <drow@false.org> wrote:

> On Thu, Nov 03, 2005 at 05:35:31PM -0800, Peter Choi
> wrote:
> > Hi,
> > 
> >   I compiled GDB6.3 on i386-linux as follow:
> >   From the source code directory (named gdb-6.3), 
> 
> >   cd ..
> >   mkdir build-gdb
> >   cd build-gdb 
> >   ../gdb-6.3/configure --target=i386-linux
> > --prefix=/home/pchoi/work/tools
> >   make
> >   make install
> > 
> >   Then I compile GDBserver on i386-linux as
> follow:
> >   From the source code directory (named gdb-6.3), 
> 
> >   cd ..
> >   mkdir build-gdbserver
> >   cd build-gdbserver 
> >   ../gdb-6.3/gdb/gdbserver/configure
> > --target=i386-linux
> --prefix=/home/pchoi/work/tools
> >   make
> >   make install
> >   
> > 
> >   Please advise whether it is correct to compile
> with
> > multithread remote debugging support???
> 
> Did gdbserver get linked to libthread_db?  Check the
> build log.
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
> 



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

  reply	other threads:[~2005-11-04  3:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  3:11 Peter Choi
2005-11-03 21:26 ` Daniel Jacobowitz
2005-11-04  1:35   ` Peter Choi
2005-11-04  3:19     ` Daniel Jacobowitz
2005-11-04  3:40       ` Peter Choi [this message]
2005-11-04  3:51         ` Daniel Jacobowitz
2005-11-04  9:06     ` Mark Kettenis

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=20051104034035.1064.qmail@web32908.mail.mud.yahoo.com \
    --to=peter_tkchoi@yahoo.com \
    --cc=drow@false.org \
    --cc=gdb@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).