From: "Frank Ch. Eigler" <fche@redhat.com>
To: "McAllister, Colin" <Colin.McAllister@garmin.com>
Cc: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Building Elfutils with Mingw32
Date: Wed, 13 Sep 2023 17:34:00 -0400 [thread overview]
Message-ID: <20230913213400.GA19324@redhat.com> (raw)
In-Reply-To: <SA2PR04MB7723A80F548491B3C0BF0BC1F4F0A@SA2PR04MB7723.namprd04.prod.outlook.com>
Hi, Colin -
> I'm currently trying to determine the level of effort required to
> compile Elfutils for Windows using MinGW. I'd like to get a version
> of Elfutils compiled with libdebginfod in order to compile GDB with
> debuginfod support on Windows. I've currently explored two
> avenues...
Nice. Please be aware of the distinct configury options to build the
debuginfod client (library linked into gdb) and the server (program).
Some of the packages you're looking for ("fts") are only used on the
server, so you wouldn't need them for your gdb project.
.../configure --help:
--enable-libdebuginfod Build debuginfod client library (can be =dummy)
--enable-debuginfod Build debuginfod server
--enable-debuginfod-urls[=URLS]
(I'm sorry I can't be more helpful with your substantial questions.)
- FChE
next prev parent reply other threads:[~2023-09-13 21:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 21:08 McAllister, Colin
2023-09-13 21:34 ` Frank Ch. Eigler [this message]
2023-09-14 6:34 ` Ulf Hermann
2023-09-14 19:44 ` McAllister, Colin
2023-09-15 6:57 ` Ulf Hermann
2023-09-15 15:42 ` McAllister, Colin
2023-09-15 21:00 ` Mark Wielaard
2023-09-16 7:17 ` Ulf Hermann
2023-09-16 7:33 ` Ulf Hermann
2023-11-01 13:05 ` Mark Wielaard
2023-09-16 19:24 ` Milian Wolff
2023-09-18 13:18 ` McAllister, Colin
2023-09-18 15:45 ` Frank Ch. Eigler
2023-11-01 13:15 ` Mark Wielaard
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=20230913213400.GA19324@redhat.com \
--to=fche@redhat.com \
--cc=Colin.McAllister@garmin.com \
--cc=elfutils-devel@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).