Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Zach Welch <zwelch@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix gdbserver build with x86_64-w64-mingw32 -m32
Date: Thu, 15 Jan 2015 04:46:00 -0000	[thread overview]
Message-ID: <20150115044605.GO8167@adacore.com> (raw)
In-Reply-To: <54B54EF2.3050901@codesourcery.com>

> Thus, the primary host for which I am building gdbserver is
> x86_64-w64-mingw32 (--host=x86_64-w64-mingw32), but I am also using the
> x86_64-w64-mingw32 toolchain to build a multilib for 32-bit windows
> (--host=x86_64-w64-mingw32 CFLAGS="-m32") as a secondary host. gdbserver
> runs on the target (and is not itself a cross compiler), so --host ==
> --target in both cases.
> 
> The primary host gdbserver build (--host=x86_64-w64-mingw32) works, but
> the secondary host build (--host=x86_64-w64-mingw32 CFLAGS="-m32") fails
> without my provided patch.

OK, IIUC, I think you want to use a 32bit mingw32 --host triplet
in this case.  The fact that the OS you'll be running gdbserver on
is 64bit does matter, your gdbserver still going to be a 32bit executable,
and therefore should be configured as such.

-- 
Joel


  reply	other threads:[~2015-01-15  4:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 17:49 Zachary T Welch
2015-01-09 20:05 ` Sergio Durigan Junior
2015-01-12 17:46   ` [PATCH v2] " Zachary T Welch
2015-01-13  9:21     ` Joel Brobecker
2015-01-10  4:17 ` [PATCH] " Joel Brobecker
2015-01-12 17:54   ` Zach Welch
2015-01-13  9:17     ` Joel Brobecker
2015-01-13 16:59       ` Zach Welch
2015-01-15  4:46         ` Joel Brobecker [this message]
2015-01-13 17:42     ` 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:
  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=20150115044605.GO8167@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=zwelch@codesourcery.com \
    /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