Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christian Biesinger <cbiesinger@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches <gdb-patches@sourceware.org>,
	Keith Marshall <keith@users.osdn.me>
Subject: Re: Cross-compiling a MinGW GDB
Date: Wed, 22 Jul 2020 12:47:36 -0500	[thread overview]
Message-ID: <CAPTJ0XGmiE8Oi_ejiHznQFaVu2nRaY0i5AeSJAubMVf77PCoaA@mail.gmail.com> (raw)
In-Reply-To: <83a6zrfq7l.fsf@gnu.org>

On Wed, Jul 22, 2020 at 11:51 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> 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 haven't done this myself but I am aware of two things:
- https://sourceware.org/gdb/wiki/CrossCompilingWithPythonSupport
- The patch discussed at
https://sourceware.org/legacy-ml/gdb-patches/2012-12/msg00754.html
claims to improve cross-compiling with python (Debian used to carry
that patch, though they've since dropped it)

Christian


  reply	other threads:[~2020-07-22 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 16:51 Eli Zaretskii
2020-07-22 17:47 ` Christian Biesinger [this message]
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=CAPTJ0XGmiE8Oi_ejiHznQFaVu2nRaY0i5AeSJAubMVf77PCoaA@mail.gmail.com \
    --to=cbiesinger@google.com \
    --cc=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