This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gdb/844: gdb compile failed, /usr/bin/ld: cannot find -lpthreads


The following reply was made to PR gdb/844; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@mvista.com>
To: ac131313@redhat.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/844: gdb compile failed, /usr/bin/ld: cannot find -lpthreads
Date: Thu, 21 Nov 2002 15:46:26 -0500

 On Thu, Nov 21, 2002 at 07:31:12PM -0000, ac131313@redhat.com wrote:
 > 
 > >Number:         844
 > >Category:       gdb
 > >Synopsis:       gdb compile failed, /usr/bin/ld: cannot find -lpthreads
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Thu Nov 21 11:38:00 PST 2002
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     ac131313@redhat.com
 > >Release:        2002-11-21
 > >Organization:
 > >Environment:
 > Red Hat GNU/Linux 7.2
 > >Description:
 > When running the testsuite, error messages like:
 > 
 > gdb compile failed, /usr/bin/ld: cannot find -lpthreads
 > 
 > appear in the output.  Given that this is just a thread compile probe, the output should be supressed.
 > 
 > Only if all the thread probes fail should an error, like:
 > 
 > UNTESTED: .... thread test
 > 
 > appear (untested?)
 
 Could be fixed by just using the common pthreads compilation function
 Jim added, IIRC...
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]