public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Claude Robitaille <claude-robitaille@hotmail.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Statically link libwinpthread-1.dll in gdbserver
Date: Mon, 2 May 2022 18:18:06 +0100	[thread overview]
Message-ID: <2646fa67-e64a-fad3-4bec-525dd05da767@palves.net> (raw)
In-Reply-To: <DS7PR07MB76860D6D05E428EFBB92C13FF7C19@DS7PR07MB7686.namprd07.prod.outlook.com>

On 2022-05-02 18:12, Claude Robitaille wrote:
> "make all-gdbserver" fails. But just make works, albeit a little longer...

"make all-gdbserver" failing is really strange.  How did it fail?  Note that should
be issued at the top level.

> 
> So, I now have a solution thanks.
> 
> Just curious. --disable-foo is nice but the problem is to get a list of foo. Is there anyway other than sifting the script and metadata files?
> 
> ./configure --help or ./configure --help-recursive are not that helpful.

I'm now aware of a way to get that list.  I think all component names match their corresponding top level directory
names, at least.  There are more directories than components, though.

  reply	other threads:[~2022-05-02 17:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 12:11 Claude Robitaille
2022-05-02 13:27 ` Pedro Alves
2022-05-02 13:33   ` Claude Robitaille
2022-05-02 13:37     ` Pedro Alves
2022-05-02 17:12       ` Claude Robitaille
2022-05-02 17:18         ` Pedro Alves [this message]
2022-05-02 17:54           ` Claude Robitaille
2022-05-02 18:39             ` Pedro Alves

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=2646fa67-e64a-fad3-4bec-525dd05da767@palves.net \
    --to=pedro@palves.net \
    --cc=claude-robitaille@hotmail.com \
    --cc=gdb@sourceware.org \
    /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).