public inbox for
 help / color / mirror / Atom feed
From: Claude Robitaille <>
To: Pedro Alves <>,
	"" <>
Subject: Re: Statically link libwinpthread-1.dll in gdbserver
Date: Mon, 2 May 2022 17:54:51 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

This is what I get with make all-gdbserver

  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>
      |           ^~~~~~~~~~~
compilation terminated.

This is the complete configuration command line I was using

export CFLAGS=-static; export CXXFLAGS=-static; ../binutils-gdb/configure --enable-static --with-static-standard-libraries --disable-gdb --host=x86_64-w64-mingw32

The binutils source I am using is
commit f0072f79e12d88ca361de04a52434430a10c5f0e (HEAD -> gdb-12-branch, origin/gdb-12-branch)

(about 2 weeks old).
From: Pedro Alves <>
Sent: May 2, 2022 1:18 PM
To: Claude Robitaille <>; <>
Subject: Re: Statically link libwinpthread-1.dll in gdbserver

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:54 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
2022-05-02 17:54           ` Claude Robitaille [this message]
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:

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