public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Claude Robitaille <claude-robitaille@hotmail.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Statically link libwinpthread-1.dll in gdbserver
Date: Mon, 2 May 2022 12:11:51 +0000	[thread overview]
Message-ID: <DS7PR07MB7686ECE8FB412C7CA135479AF7C19@DS7PR07MB7686.namprd07.prod.outlook.com> (raw)

Hi,

I am trying to produce a statically linked gdbserver (except the distribution DLL from Windows). I have everything in except for libwinpthread-1.dll. I
guess gdbserver should be linked with libwinpthread.a but how to tell the build system to do so?

I am using this command line to configure:
../binutils-gdb/configure --enable-static --with-static-standard-libraries --disable-gdb --host=x86_64-w64-mingw32

and then followed by
make

Using objdump, I see that the following DLL are needed by the binary
KERNEL32.dll
msvcrt.dll
libwinpthread-1.dll
USER32.dll
WS2_32.dll

As you can see from the command line, I am using mingw-w64. I am using the stock Ubuntu 20.04 package for it, which includes the following library files for pthread
-rw-r--r-- 1 root root 388692 Nov 15  2019 libpthread.a
-rw-r--r-- 1 root root  88994 Nov 15  2019 libpthread.dll.a
-rwxr-xr-x 1 root root 621013 Nov 15  2019 libwinpthread-1.dll
-rw-r--r-- 1 root root 388692 Nov 15  2019 libwinpthread.a
-rw-r--r-- 1 root root  88994 Nov 15  2019 libwinpthread.dll.a



             reply	other threads:[~2022-05-02 12:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 12:11 Claude Robitaille [this message]
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
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=DS7PR07MB7686ECE8FB412C7CA135479AF7C19@DS7PR07MB7686.namprd07.prod.outlook.com \
    --to=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).