public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Claude Robitaille <claude-robitaille@hotmail.com>
To: Pedro Alves <pedro@palves.net>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Statically link libwinpthread-1.dll in gdbserver
Date: Mon, 2 May 2022 17:12:10 +0000	[thread overview]
Message-ID: <DS7PR07MB76860D6D05E428EFBB92C13FF7C19@DS7PR07MB7686.namprd07.prod.outlook.com> (raw)
In-Reply-To: <12aa0d4e-4225-4e7e-4443-8dee1e53092f@palves.net>

"make all-gdbserver" fails. But just make works, albeit a little longer...

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.

________________________________
From: Pedro Alves <pedro@palves.net>
Sent: May 2, 2022 9:37 AM
To: Claude Robitaille <claude-robitaille@hotmail.com>; gdb@sourceware.org <gdb@sourceware.org>
Subject: Re: Statically link libwinpthread-1.dll in gdbserver

On 2022-05-02 14:33, Claude Robitaille wrote:
> Pedro Alves wrote:
> Have you tried passing "-static" in CFLAGS/CXXFLAGS?
>
> No. I did not try.
>
> But, if I do this on the top level configure command line, wouldn't then everything be statically linked? Is it possible to pass this falg only to the gdbserver configure command?

No, but you can use --disable-foo / --disable-foo to control which top level components
you want to build, and/or use "make all-gdbserver" to build just gdbserver.

  reply	other threads:[~2022-05-02 17:12 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 [this message]
2022-05-02 17:18         ` Pedro Alves
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=DS7PR07MB76860D6D05E428EFBB92C13FF7C19@DS7PR07MB7686.namprd07.prod.outlook.com \
    --to=claude-robitaille@hotmail.com \
    --cc=gdb@sourceware.org \
    --cc=pedro@palves.net \
    /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).