From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Cc: Keith Marshall <keith@users.osdn.me>
Subject: Cross-compiling a MinGW GDB
Date: Wed, 22 Jul 2020 19:51:26 +0300 [thread overview]
Message-ID: <83a6zrfq7l.fsf@gnu.org> (raw)
Does anyone build their MinGW GDB by cross-compiling it on GNU/Linux?
If so, could you please share your experience with specifying the
Python tree during the build, such that the built GDB will be able to
use Python features on the target Windows systems?
I'm asking because Kieth Marshall is trying to build a recent GDB this
way, to update the binaries offered by the MinGW site, and he bumps
into all kinds of annoying problems, see, for example, the discussion
starting here:
https://osdn.net/projects/mingw/lists/archive/users/2020-July/000607.html
If someone could provide practical advice how to avoid these
annoyances, It would probably make Keith's job much more pleasant and
less time-consuming.
I always build GDB natively, so I never had to deal with any of these
problems.
TIA
next reply other threads:[~2020-07-22 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 16:51 Eli Zaretskii [this message]
2020-07-22 17:47 ` Christian Biesinger
2020-07-22 19:58 ` Keith Marshall
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=83a6zrfq7l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=keith@users.osdn.me \
/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