public inbox for
 help / color / mirror / Atom feed
From: Claude Robitaille <>
To: Shahab Vahedi <>
Cc: Gdb <>
Subject: Re: Building gdbserver
Date: Mon, 18 Apr 2022 01:40:15 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

What is the best way to link gdbserver statically?

I now the following configure command line

../binutils-gdb/configure --disable-shared --enable-static --with-static-standard-libraries --disable-gdb --host=x86_64-w64-mingw32

But I still have a dependency on libwinpthread-1.dll (and the Windows system DLL, which are OK).
From: Claude Robitaille <>
Sent: April 17, 2022 3:40 PM
To: Shahab Vahedi <>; Claude Robitaille <>
Cc: Gdb <>
Subject: Re: Building gdbserver

Doing a full make worked.

I guess that a needed path gets added to the include argument list in some other tool.
From: Gdb <> on behalf of Claude Robitaille via Gdb <>
Sent: April 17, 2022 2:07 PM
To: Shahab Vahedi <>
Cc: Gdb <>
Subject: Re: Building gdbserver

Same result.
From: Shahab Vahedi <>
Sent: April 17, 2022 1:19 PM
To: Claude Robitaille <>
Cc: Gdb <>
Subject: Re: Building gdbserver

On Sun, Apr 17, 2022 at 03:12:37PM +0000, Claude Robitaille wrote:
> I get this:
> make[1]: Entering directory '/mnt/data/sbox/tools/'
>   CXX    alloc.o
> In file included from ../../binutils-gdb/gdbserver/../gdbsupport/common-defs.h:197,
>                  from ../../binutils-gdb/gdbserver/../gdb/alloc.c:37:
> ../../binutils-gdb/gdbserver/../gdbsupport/gdb_locale.h:27:11: fatal error: libintl.h: No such file or directory
>    27 | # include <libintl.h>

Try adding "--disable-gdb" to the "configure" command.


  reply	other threads:[~2022-04-18  1:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-17  3:35 Claude Robitaille
2022-04-17 10:23 ` Shahab Vahedi
2022-04-17 15:12   ` Claude Robitaille
2022-04-17 17:19     ` Shahab Vahedi
2022-04-17 18:07       ` Claude Robitaille
2022-04-17 19:40         ` Claude Robitaille
2022-04-18  1:40           ` Claude Robitaille [this message]
2022-04-18 15:38     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).