public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [pushed] [gdb/testsuite] Fix untested in gdb.base/frame-view.exp
Date: Mon, 23 Jan 2023 11:12:52 -0500	[thread overview]
Message-ID: <8cf44786-9ec3-8d14-24b7-41fdbb39b24f@simark.ca> (raw)
In-Reply-To: <20230123075939.1771-1-tdevries@suse.de>



On 1/23/23 02:59, Tom de Vries via Gdb-patches wrote:
> When running test-case gdb.base/frame-view.exp, I see:
> ...
> gdb compile failed, ld: frame-view0.o: in function `main':
> frame-view.c:73: undefined reference to `pthread_create'
> ld: frame-view.c:76: undefined reference to `pthread_join'
> collect2: error: ld returned 1 exit status
> UNTESTED: gdb.base/frame-view.exp: failed to prepare
> ...
> 
> Fix this by adding pthreads to the compilation flags.

Thanks for fixing this.  I suppose it worked on my machines because they
use newer glibcs where pthread is integrated into libc?

Simon

  reply	other threads:[~2023-01-23 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23  7:59 Tom de Vries
2023-01-23 16:12 ` Simon Marchi [this message]
2023-01-23 16:29   ` Tom de Vries

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=8cf44786-9ec3-8d14-24b7-41fdbb39b24f@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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).